 |
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
| Datasheet File OCR Text: |
| document number: 319973-003 intel ? i/o controller hub 10 (ich10) family datasheet october 2008 http://www..net/ datasheet pdf - http://www..net/
2 datasheet legal lines and disclaimers information in this document is provided in connection with in tel? products. no license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by th is document. except as provided in intel's terms and conditions of sale for such products, intel assumes no liability whatsoever, and intel disclaims any express or implied warranty, relating to sale and/or use of intel products including liability or warranties relating to fitness for a particular purpose, merchantability, or infringement of any patent , copyright or other intellectual property right. unless otherwise agreed in writing by intel, the intel products are not designed nor intended for any application in which the failure of the intel product could create a situation where personal injury or death may occur. intel may make changes to specifications and product descriptions at any time, without notice. designers must not rely on the a bsence or characteristics of any features or instructions marked "res erved" or "undefined." intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. the information here is subject to change without notic e. do not finalize a design with this information. the intel ? i/o controller hub 10 (ich10) family chipset component may contai n design defects or errors known as errata which may cause th e product to deviate from published specifications. curren t characterized errata ar e available on request. contact your local intel sales office or your distributor to obtain the latest specifications and before placing your product o rder. i 2 c is a two-wire communications bus/protocol developed by philips. smbus is a subset of the i 2 c bus/protocol and was developed by intel. implementations of the i 2 c bus/protocol may require licenses from various entities, in cluding philips electronics n.v. and north american philips corporation. intel ? active management technology requires the computer system to have an intel ? amt-enabled chipset, network hard ware and software, as well as connection with a power source and a corporate network connection . setup requires configuration by the purchaser and may requi re scripting with the management console or further integration into existing security frameworks to enable certain functionality. it may also requi re modifications of implementation of new business processes. with regard to noteb ooks, intel amt may not be available or certain capabilities may be limited over a host os-based vpn or when connecting wirelessly, on battery power, sleeping, hibernating or powered off. for more information, see www.intel.com/technology/platform-technology/intel-amt/ intel ? virtualization technology requires a computer system with an enabled intel ? processor, bios, virtual machine monitor (vmm) and, for some uses, certain computer system software enabled for it. functionality, pe rformance or other benefits will vary depending on hardware a nd software configurations and may require a bios update . software applications may not be compatible with all operating systems. please ch eck with your application vendor. no computer system can provide absolute security under all conditions. intel ? trusted execution technology (intel ? txt) requires a computer system with intel ? virtualization technology, an intel txt-enabled processor, chip set, bios, authenticated code modules and an intel txt-compatib le measured launched environment (mle). the mle could consist of a virtual machine monitor, an os or an application. in addition, intel tx t requires the system to contain a tpm v1.2, as defined by the trusted computing group and specific software for some uses. for more information, see http://www.intel.com/technology/security home networking capability and many intel ? viiv? technology-based usage models will require ad ditional hardware devices, software or services. functionality of intel ? viiv? technology verified devices will vary; check product de tails for desired features. system and component performance and functionality will vary depending on your specific hardware and software configurations. see www.intel.com/go/viiv_info for mor e information. intel ? high definition audio requires a system wi th an appropriate intel chipset and a mother board with an appropriate codec and the n ecessary drivers installed. system sound quality will vary depending on actual implementation, controller, codec, drivers and speakers. for more information about intel ? hd audio, refer to http://www.intel.com/ intel, intel logo, intel speedstep, intel viiv, and intel vpro ar e trademarks of intel corporation in the u.s. and other countr ies. *other names and brands may be claimed as the property of others. copyright ? 2008, intel corporation http://www..net/ datasheet pdf - http://www..net/ datasheet 3 contents 1introduction ............................................................................................................ 33 1.1 about this manual ............................................................................................. 33 1.2 overview ......................................................................................................... 37 1.2.1 capability overview .... ........... .......... ........... ........... ............ ......... ............ 39 1.3 intel ? ich10 family high-level component differences ......................................... 44 2 signal description ................................................................................................... 45 2.1 direct media interface (dmi) to host controller ..................................................... 47 2.2 pci express* interface....................................................................................... 48 2.3 lan connect interface ....................................................................................... 48 2.4 gigabit lan connect interface ............................................................................ 49 2.5 firmware hub interface...................................................................................... 50 2.6 pci interface .................................................................................................... 50 2.7 serial ata interface........................................................................................... 52 2.8 lpc interface.................................................................................................... 55 2.9 interrupt interface ............................................................................................ 55 2.10 usb interface ................................................................................................... 56 2.11 power management interface.............................................................................. 58 2.12 processor interface............................................................................................ 61 2.13 smbus interface................................................................................................ 62 2.14 system management interface............................................................................ 63 2.15 real time clock interface ................................................................................... 64 2.16 other clocks..................................................................................................... 65 2.17 miscellaneous signals ........................................................................................ 65 2.18 intel ? high definition audio link ......................................................................... 66 2.19 serial peripheral interface (spi) .......................................................................... 67 2.20 controller link .................................................................................................. 68 2.21 intel ? quiet system technology ......................................................................... 68 2.22 jtag signals (intel ? ich10 corporate family only) ............................................... 69 2.23 general purpose i/o signals ............................................................................... 70 2.24 power and ground signals .................................................................................. 73 2.25 pin straps ........................................................................................................ 75 2.25.1 functional straps ................................................................................... 75 2.25.2 external rtc circuitry ............................................................................. 79 3intel ? ich10 pin states ........................................................................................... 81 3.1 integrated pull-ups and pull-downs ..................................................................... 81 3.2 output and i/o signals planes and states............................................................. 83 3.3 power planes for input signals ............................................................................ 88 4intel ? ich10 and system clock domains ................................................................. 91 5 functional description ............................................................................................. 93 5.1 dmi-to-pci bridge (d30:f0) ............................................................................... 93 5.1.1 pci bus interface ................................................................................... 93 5.1.2 pci bridge as an initiator ........................................................................ 93 5.1.3 parity error detection and generation ....................................................... 95 5.1.4 pcirst# ............................................................................................... 96 5.1.5 peer cycles ........................................................................................... 96 5.1.6 pci-to-pci bridge model.......................................................................... 96 5.1.7 idsel to device number mapping ............................................................ 97 5.1.8 standard pci bus configuration mechanism ............................................... 97 5.2 pci express* root ports (d28:f0,f1,f2,f3,f4,f5).................................................. 97 5.2.1 interrupt generation............................................................................... 97 5.2.2 power management ................................................................................ 98 5.2.3 serr# generation ................................................................................. 99 5.2.4 hot-plug ............................................................................................. 100 5.3 gigabit ethernet controller (b0:d25:f0)............................................................. 101 5.3.1 gigabit ethernet pci bus interface.......................................................... 102 5.3.2 error events and error reporting ............................................................ 103 5.3.3 ethernet interface ................................................................................ 103 5.3.4 pci power management ........................................................................ 104 5.3.5 configurable leds ................................................................................ 105 http://www..net/ datasheet pdf - http://www..net/ 4 datasheet 5.3.6 function level reset support (flr) ......................................................... 106 5.4 lpc bridge (w/ system and management functi ons) (d31:f0) ............................... 107 5.4.1 lpc interface ....................................................................................... 107 5.5 dma operation (d31:f0) .................................................................................. 112 5.5.1 channel priority.................................................................................... 113 5.5.2 address compatibility mode .... ............ ........... ........... ............ ........... ...... 113 5.5.3 summary of dma transfer sizes ............................................................. 114 5.5.4 autoinitialize ........................................................................................ 114 5.5.5 software commands ............................................................................. 115 5.6 lpc dma ........................................................................................................ 115 5.6.1 asserting dma requests ........................................................................ 115 5.6.2 abandoning dma requests..................................................................... 116 5.6.3 general flow of dma transfers ............................................................... 116 5.6.4 terminal count..................................................................................... 116 5.6.5 verify mode ......................................................................................... 117 5.6.6 dma request deassertion ...................................................................... 117 5.6.7 sync field / ldrq# rules ..................................................................... 118 5.7 8254 timers (d31:f0) ...................................................................................... 118 5.7.1 timer programming .............................................................................. 119 5.7.2 reading from the interval timer ............................................................. 120 5.8 8259 interrupt controllers (pic) (d31:f0)........................................................... 121 5.8.1 interrupt handling ................................................................................ 122 5.8.2 initialization command words (icwx) ..................................................... 123 5.8.3 operation command words (ocw) ......................................................... 124 5.8.4 modes of operation ............................................................................... 124 5.8.5 masking interrupts................................................................................ 127 5.8.6 steering pci interrupts.......................................................................... 127 5.9 advanced programmable interrupt controller (apic) (d31:f0)............................... 128 5.9.1 interrupt handling ................................................................................ 128 5.9.2 interrupt mapping................................................................................. 128 5.9.3 pci / pci express* message-based interrupts .......................................... 129 5.9.4 front side bus interrupt delivery ............................................................ 129 5.9.5 ioxapic address remapping .................................................................. 131 5.9.6 external interrupt controller support ...................................................... 131 5.10 serial interrupt (d31:f0) .................................................................................. 132 5.10.1 start frame ......................................................................................... 132 5.10.2 data frames ........................................................................................ 133 5.10.3 stop frame.......................................................................................... 133 5.10.4 specific interrupts not supported via serirq........................................... 133 5.10.5 data frame format............................................................................... 134 5.11 real time clock (d31:f0) ................................................................................. 135 5.11.1 update cycles ...................................................................................... 135 5.11.2 interrupts ............................................................................................ 136 5.11.3 lockable ram ranges............................................................................ 136 5.11.4 century rollover................................................................................... 136 5.11.5 clearing battery-backed rtc ram........................................................... 136 5.12 processor interface (d31:f0) ............................................................................ 138 5.12.1 processor interface signals .................................................................... 138 5.12.2 dual-processor issues ........................................................................... 141 5.13 power management (d31:f0) ............................................................................ 142 5.13.1 features .............................................................................................. 142 5.13.2 intel ? ich10 and system power states ................................................... 142 5.13.3 system power planes ............................................................................ 145 5.13.4 smi#/sci generation............................................................................ 145 5.13.5 dynamic processor clock control .............. .............................................. 148 5.13.6 sleep states ........................................................................................ 151 5.13.7 thermal management............................................................................ 154 5.13.8 event input signals and their usage ....................................................... 155 5.13.9 alt access mode .................................................................................. 158 5.13.10system power supplies, planes, and signals............................................. 162 5.13.11clock generators .................................................................................. 164 5.13.12legacy power management theory of operation ....................................... 165 5.13.13reset behavior ..................................................................................... 165 5.14 system management (d31:f0) .......................................................................... 167 5.14.1 theory of operation .............................................................................. 167 5.14.2 tco modes .......................................................................................... 169 5.15 general purpose i/o (d31:f0) ........................................................................... 173 http://www..net/ datasheet pdf - http://www..net/ datasheet 5 5.15.1 power wells......................................................................................... 173 5.15.2 smi# and sci routing .......................................................................... 173 5.15.3 triggering ........................................................................................... 173 5.15.4 gpio registers lockdown ...................................................................... 173 5.15.5 serial post codes over gpio ................................................................ 174 5.15.6 intel management engine gpios ............................................................ 176 5.16 sata host controller (d31:f2, f5) .................................................................... 176 5.16.1 sata feature support........................................................................... 177 5.16.2 theory of operation.............................................................................. 178 5.16.3 sata swap bay support ....................................................................... 178 5.16.4 hot plug operation ............................................................................... 178 5.16.5 function level reset support (flr) ........................................................ 179 5.16.6 intel ? matrix storage technology configuration ....................................... 180 5.16.7 power management operation................................................................ 181 5.16.8 sata device presence........................................................................... 183 5.16.9 sata led............................................................................................ 184 5.16.10ahci operation.................................................................................... 184 5.16.11serial ata reference clock low power request (sataclkreq#) ................ 184 5.16.12sgpio signals ..................................................................................... 185 5.16.13external sata...................................................................................... 189 5.17 high precision event timers.............................................................................. 189 5.17.1 timer accuracy .................................................................................... 189 5.17.2 interrupt mapping ................................................................................ 190 5.17.3 periodic vs. non-periodic modes ............................................................. 190 5.17.4 enabling the timers.............................................................................. 191 5.17.5 interrupt levels ................................................................................... 191 5.17.6 handling interrupts .............................................................................. 192 5.17.7 issues related to 64-bit timers with 32- bit processors .............................. 192 5.18 usb uhci host controllers (d29:f0, f1, f2, f3 and d26:f0, f1 and f2) ................. 192 5.18.1 data structures in main memory............. ................................................ 193 5.18.2 data transfers to/from main memory ...................................................... 193 5.18.3 data encoding and bit stuffing ............................................................... 193 5.18.4 bus protocol ........................................................................................ 193 5.18.5 packet formats .................................................................................... 194 5.18.6 usb interrupts..................................................................................... 194 5.18.7 usb power management ....................................................................... 197 5.18.8 usb legacy keyboard operation ............................................................ 197 5.18.9 function level reset support (flr) ........................................................ 200 5.19 usb ehci host controllers (d29:f7 and d26:f7)................................................. 201 5.19.1 ehc initialization.................................................................................. 201 5.19.2 data structures in main memory............. ................................................ 202 5.19.3 usb 2.0 enhanced host controller dma................................................... 202 5.19.4 data encoding and bit stuffing ............................................................... 202 5.19.5 packet formats .................................................................................... 203 5.19.6 usb 2.0 interrupts and error conditions .................................................. 203 5.19.7 usb 2.0 power management .................................................................. 204 5.19.8 interaction with uhci host controllers .... ................................................ 205 5.19.9 usb 2.0 legacy keyboard operation ....................................................... 208 5.19.10usb 2.0 based debug port .................................................................... 209 5.19.11usb pre-fetch based pause ................................................................... 213 5.19.12function level reset support (flr) ........................................................ 214 5.20 smbus controller (d31:f3) ............................................................................... 214 5.20.1 host controller..................................................................................... 215 5.20.2 bus arbitration..................................................................................... 219 5.20.3 bus timing .......................................................................................... 220 5.20.4 interrupts / smi#................................................................................. 221 5.20.5 smbalert# ........................................................................................ 222 5.20.6 smbus crc generation and checking...................................................... 222 5.20.7 smbus slave interface .......................................................................... 222 5.21 intel ? high definition audio overview ................................................................ 228 5.22 intel ? active management technology (intel ? amt) (corporate only).................... 228 5.22.1 intel ? amt features ............................................................................. 229 5.22.2 intel ? amt requirements ...................................................................... 229 5.23 serial peripheral interface (spi) ........................................................................ 229 5.23.1 spi supported feature overview ............................................................ 230 5.23.2 flash descriptor ................................................................................... 232 5.23.3 flash access ........................................................................................ 234 http://www..net/ datasheet pdf - http://www..net/ 6 datasheet 5.23.4 serial flash device compatibility requirements ........................................ 235 5.23.5 multiple page write usage model............................................................. 237 5.23.6 flash device configurations ................................................................... 238 5.23.7 spi flash device recommended pinout.................................................... 238 5.23.8 serial flash device package ................................................................... 239 5.24 intel ? quiet system technology (intel ? qst) ..................................................... 240 5.24.1 pwm outputs ....................................................................................... 240 5.24.2 tach inputs ........................................................................................ 240 5.25 thermal sensors.............................................................................................. 240 5.26 feature capability mechanism ...... ............ ........... ............ ........... .......... ............. 241 5.27 integrated trusted platform module (corporate only) ........................................... 241 5.27.1 integrated tpm hardware requirements .................................................. 241 5.27.2 enabling integrated tpm ........................................................................ 242 6 ballout definition ................................................................................................... 243 6.1 intel ? ich10 ballout ....................................................................................... 243 7 package information ............................................................................................. 253 7.1 intel ? ich10 package ...................................................................................... 253 8 electrical characteristics ........................................................................................ 255 8.1 thermal specifications...................................................................................... 255 8.2 absolute maximum ratings ............................................................................... 255 8.3 dc characteristics ........................................................................................... 255 8.4 ac characteristics............................................................................................ 268 8.5 timing diagrams ............................................................................................. 280 9 register and memory mapping ............................................................................... 293 9.1 pci devices and functions ................................................................................ 294 9.2 pci configuration map ...................................................................................... 295 9.3 i/o map.......................................................................................................... 295 9.3.1 fixed i/o address ranges ...................................................................... 295 9.3.2 variable i/o decode ranges ................................................................... 298 9.4 memory map ................................................................................................... 299 9.4.1 boot-block update scheme .................................................................... 300 10 chipset configur ation registers ............................................................................. 303 10.1 chipset configuration registers (memory space) ................................................. 303 10.1.1 vch?virtual channel capability header re gister ........... .......... ........... ...... 306 10.1.2 vcap1?virtual channel capability #1 regist er .............. .......... ........... ...... 306 10.1.3 vcap2?virtual channel capability #2 regist er .............. .......... ........... ...... 307 10.1.4 pvc?port virtual channel control register............................................... 307 10.1.5 pvs?port virtual channel status register................................................ 307 10.1.6 v0cap?virtual channel 0 resource capab ility register.... ................ .......... 308 10.1.7 v0ctl?virtual channel 0 resource control register ................................. 308 10.1.8 v0sts?virtual channel 0 resource status register .................................. 309 10.1.9 v1cap?virtual channel 1 resource capab ility register.... ................ .......... 309 10.1.10v1ctl?virtual channel 1 resource control register ................................. 310 10.1.11v1sts?virtual channel 1 resource status register .................................. 310 10.1.12pat?port arbitration table (consumer only) ........................................... 311 10.1.13cir1?chipset initialization register 1 ..... ................................................ 311 10.1.14rec?root error command register ........................................................ 311 10.1.15rctcl?root complex topology capabilitie s list register ........ ............ ...... 312 10.1.16esd?element self description register ................................................... 312 10.1.17uld?upstream link descriptor register .................................................. 312 10.1.18ulba?upstream link base address register ............................................ 313 10.1.19rp1d?root port 1 descriptor register..................................................... 313 10.1.20rp1ba?root port 1 base address register............................................... 313 10.1.21rp2d?root port 2 descriptor register..................................................... 314 10.1.22rp2ba?root port 2 base address register............................................... 314 10.1.23rp3d?root port 3 descriptor register..................................................... 314 10.1.24rp3ba?root port 3 base address register............................................... 315 10.1.25rp4d?root port 4 descriptor register..................................................... 315 10.1.26rp4ba?root port 4 base address register............................................... 315 10.1.27hdd?intel ? high definition audio descriptor register............................... 316 10.1.28 hdba?intel ? high definition audio base address register......................... 316 10.1.29rp5d?root port 5 descriptor register..................................................... 316 10.1.30rp5ba?root port 5 base address register............................................... 317 http://www..net/ datasheet pdf - http://www..net/ datasheet 7 10.1.31rp6d?root port 6 descriptor register .................................................... 317 10.1.32rp6ba?root port 6 base address register .............................................. 317 10.1.33ilcl?internal link capabilities list regist er .......... ........... ........... ............ 318 10.1.34lcap?link capabilities register ............................................................. 318 10.1.35lctl?link control register ................................................................... 318 10.1.36lsts?link status register .................................................................... 319 10.1.37cir2 ? chipset initialization register 2................................................... 319 10.1.38cir3 ? chipset initialization register 3................................................... 319 10.1.39bcr ? backbone configuration register.................................................. 319 10.1.40rpc?root port configuration register ...... .............................................. 320 10.1.41dmic?dmi control register .................................................................. 321 10.1.42rpfn?root port function number and hide for pci express* root ports ..... 321 10.1.43flrstat?flr pending status register ................................................... 323 10.1.44cir13?chipset initialization register 13 ................................................. 324 10.1.45cir5?chipset initialization register 5..... ................................................ 324 10.1.46trsr?trap status register ................................................................... 324 10.1.47trcr?trapped cycle register ............................................................... 325 10.1.48twdr?trapped write data register......... .............................................. 325 10.1.49iotrn ? i/o trap register (0-3)............................................................ 326 10.1.50dmc?dmi miscellaneous control register ............................................... 327 10.1.51cir6?chipset initialization register 6..... ................................................ 327 10.1.52cir7?chipset initialization register 7..... ................................................ 327 10.1.53tctl?tco configuration register .......................................................... 328 10.1.54d31ip?device 31 interrupt pin register.................................................. 329 10.1.55d30ip?device 30 interrupt pin register.................................................. 330 10.1.56d29ip?device 29 interrupt pin register.................................................. 330 10.1.57d28ip?device 28 interrupt pin register.................................................. 331 10.1.58d27ip?device 27 interrupt pin register.................................................. 332 10.1.59d26ip?device 26 interrupt pin register.................................................. 333 10.1.60d25ip?device 25 interrupt pin register.................................................. 334 10.1.61d31ir?device 31 interrupt route register ............................................. 334 10.1.62d30ir?device 30 interrupt route register ............................................. 335 10.1.63d29ir?device 29 interrupt route register ............................................. 336 10.1.64d28ir?device 28 interrupt route register ............................................. 337 10.1.65d27ir?device 27 interrupt route register ............................................. 338 10.1.66d26ir?device 26 interrupt route register ............................................. 339 10.1.67d25ir?device 25 interrupt route register ............................................. 340 10.1.68oic?other interrupt control register (corporate only) ............................ 341 10.1.69oic?other interrupt control register (consumer only) ............................ 341 10.1.70sbemc3?scheduled break event c3 exit latency..................................... 342 10.1.71sbemc4?scheduled break event c4 exit latency..................................... 342 10.1.72prsts?power and reset status (corporate only) .................................... 343 10.1.73rc?rtc configuration register ............................................................. 344 10.1.74hptc?high precision timer configuration register ................................... 344 10.1.75gcs?general control and status register............................................... 345 10.1.76buc?backed up control register ........................................................... 347 10.1.77fd?function disable register ................ ................................................ 348 10.1.78cg?clock gating ................................................................................. 350 10.1.79fdsw?function disable sus well ............ .............................................. 352 10.1.80cir8?chipset initialization register 8..... ................................................ 352 10.1.81cir9?chipset initialization register 9..... ................................................ 352 10.1.82ppo?port power off ............................................................................. 352 10.1.83cir10?chipset initialization register 10 ................................................. 353 10.1.84map?remap control register ................................................................ 353 11 pci-to-pci bridge registers (d30:f0) ................................................................... 355 11.1 pci configuration registers (d30:f0)................................................................. 355 11.1.1 vid? vendor identification register (p ci-pci?d30:f0) ............................ 356 11.1.2 did? device identification register (pci-pci?d30:f0)............................. 356 11.1.3 pcicmd?pci command (pci-pci?d30:f0)............................................. 357 11.1.4 psts?pci status register (pci-pci?d30:f0) ......................................... 357 11.1.5 rid?revision identification register (p ci-pci?d30:f0) ........................... 359 11.1.6 cc?class code register (pci-pci?d30:f0) ............................................ 359 11.1.7 pmlt?primary master latency timer register (pci-pci?d30:f0) ............................................................................... 360 11.1.8 headtyp?header type register (pci-pci?d30:f0) ................................. 360 11.1.9 bnum?bus number register (pci-pci?d30:f0) ...................................... 360 http://www..net/ datasheet pdf - http://www..net/ 8 datasheet 11.1.10smlt?secondary master latency timer register (pci-pci?d30:f0)................................................................................ 361 11.1.11iobase_limit?i/o base and limit register (pci-pci?d30:f0)................................................................................ 361 11.1.12secsts?secondary status register (pci-pci?d30:f0) ............................ 362 11.1.13membase_limit?memory base and limit register (pci-pci?d30:f0)................................................................................ 363 11.1.14pref_mem_base_limit?prefetchable memory base and limit register (pci-pci?d30:f0) ..................................................... 363 11.1.15pmbu32?prefetchable memory base upper 32 bits register (pci-pci?d30:f0) ................................................................... 364 11.1.16pmlu32?prefetchable memory limit upper 32 bits register (pci-pci?d30:f0) ................................................................... 364 11.1.17capp?capability list pointer register (p ci-pci?d30:f0) ........ ............ ...... 364 11.1.18intr?interrupt information register (p ci-pci?d30:f0) ........................... 364 11.1.19bctrl?bridge control register (pci-pci?d30:f0) ................................... 365 11.1.20spdh?secondary pci device hiding register (pci-pci?d30:f0)................................................................................ 366 11.1.21dtc?delayed transaction control register (pci-pci?d30:f0)................................................................................ 367 11.1.22bps?bridge proprietary status register (pci-pci?d30:f0)................................................................................ 368 11.1.23 bpc?bridge policy configuration register (pci-pci?d30:f0)................................................................................ 369 11.1.24svcap?subsystem vend or capability register (pci-pci?d30:f0)................................................................................ 370 11.1.25svid?subsystem vendor ids register (pci-pci?d30:f0) ......................... 370 12 gigabit lan config uration registers ...................................................................... 371 12.1 gigabit lan configuration registers (gigabit lan ? d25:f0)................................. 371 12.1.1 vid?vendor identification register (gigabit lan?d25:f0) .......................................................................... 372 12.1.2 did?device identification register (gigabit lan?d25:f0) .......................................................................... 372 12.1.3 pcicmd?pci command register (gigabit lan?d25:f0) .......................................................................... 373 12.1.4 pcists?pci status register (gigabit lan?d25:f0) .......................................................................... 374 12.1.5 rid?revision identification register (gigabit lan?d25:f0) .......................................................................... 375 12.1.6 cc?class code register (gigabit lan?d25:f0) .......................................................................... 375 12.1.7 cls?cache line size register (gigabit lan?d25:f0) .......................................................................... 375 12.1.8 plt?primary latency timer register (gigabit lan?d25:f0) .......................................................................... 375 12.1.9 ht?header type register (gigabit lan?d25:f0) .......................................................................... 375 12.1.10mbara?memory base address register a (gigabit lan?d25:f0) .......................................................................... 376 12.1.11mbarb?memory base address register b (gigabit lan?d25:f0) .......................................................................... 376 12.1.12mbarc?memory base address register c (gigabit lan?d25:f0) .......................................................................... 377 12.1.13svid?subsystem vendor id register (gigabit lan?d25:f0) .......................................................................... 377 12.1.14sid?subsystem id register (gigabit lan?d25:f0) .......................................................................... 377 12.1.15erba?expansion rom base address register (gigabit lan?d25:f0) .......................................................................... 377 12.1.16capp?capabilities list pointer register (gigabit lan?d25:f0) .......................................................................... 378 12.1.17intr?interrupt information register (gigabit lan?d25:f0) .......................................................................... 378 12.1.18mlmg?maximum latency/minimum grant register (gigabit lan?d25:f0) .......................................................................... 378 http://www..net/ datasheet pdf - http://www..net/ datasheet 9 12.1.19clist 1?capabilities list register 1 (gigabit lan?d25:f0).......................................................................... 378 12.1.20pmc?pci power management capabilities register (gigabit lan?d25:f0).......................................................................... 379 12.1.21pmcs?pci power management control and status register (gigabit lan?d25:f0) ............................................................. 380 12.1.22dr?data register (gigabit lan?d25:f0).......................................................................... 381 12.1.23clist 2?capabilities list register 2 (gigabit lan?d25:f0).......................................................................... 381 12.1.24mctl?message control register (gigabit lan?d25:f0).......................................................................... 381 12.1.25maddl?message address low register (gigabit lan?d25:f0).......................................................................... 382 12.1.26maddh?message address high register (gigabit lan?d25:f0).......................................................................... 382 12.1.27mdat?message data register (gigabit lan?d25:f0).......................................................................... 382 12.1.28flrcap?function level reset capability (gigabit lan?d25:f0).......................................................................... 382 12.1.29flrclv?function level reset capability length and version (gigabit lan?d25:f0).......................................................................... 383 12.1.30devctrl?device control (gigabit lan?d25:f0) ..................................... 383 12.2 mbara?gigabit lan base address a registers ................................................... 384 12.2.1 ldr4?lan device initialization register 4 (gigabit lan memory mapped base address register) ............................... 384 12.2.2 ldr3?lan device initialization register 3 (gigabit lan memory mapped base address register) ............................... 384 12.2.3 ldcr2?lan device control register 2 (gigabit lan memory mapped base address register) ............................... 385 12.2.4 ldcr4?lan device control register 4 (gigabit lan memory mapped base address register) ............................... 385 12.2.5 ldr5?lan device control register 5 (gigabit lan memory mapped base address register) ............................... 385 12.2.6 ldr1?lan device initialization register 1 (gigabit lan memory mapped base address register) ............................... 385 13 lpc interface bridge registers (d31:f0) ............................................................... 387 13.1 pci configuration registers (lpc i/f?d31:f0) .................................................... 387 13.1.1 vid?vendor identification register (lpc i/f?d31:f0).............................. 389 13.1.2 did?device identification register (lpc i/f?d31:f0) .............................. 389 13.1.3 pcicmd?pci command register (lpc i/f?d31:f0) ................................ 389 13.1.4 pcists?pci status register (lpc i/f?d31:f0) ....................................... 390 13.1.5 rid?revision identification register (l pc i/f?d31:f0) ............................ 391 13.1.6 pi?programming interface register (lpc i/f?d31:f0) ............................. 391 13.1.7 scc?sub class code register (lpc i/f?d31:f0)..................................... 391 13.1.8 bcc?base class code register (lpc i/f?d31:f0) ................................... 391 13.1.9 plt?primary latency timer register (lpc i/f?d31:f0)............................ 391 13.1.10 headtyp?header type register (lpc i/f?d31:f0) ................................. 392 13.1.11ss?sub system identifiers register (lpc i/f?d31:f0) ............................ 392 13.1.12pmbase?acpi base address register (lpc i/f?d31:f0) .......................... 392 13.1.13acpi_cntl?acpi control register (lpc i/f ? d31:f0)............................. 393 13.1.14gpiobase?gpio base address register (lpc i/f ? d31:f0)..................... 393 13.1.15gc?gpio control register (lpc i/f ? d31:f0)........................................ 394 13.1.16pirq[n]_rout?pirq[a,b,c,d] routing control register (lpc i/f?d31:f0) ................................................................................ 395 13.1.17sirq_cntl?serial irq control register (lpc i/f?d31:f0)....................... 396 13.1.18pirq[n]_rout?pirq[e,f,g,h] routing control register (lpc i/f?d31:f0) ................................................................................ 397 13.1.19lpc_ibdf?ioxapic bus:device:function (lpc i/f?d31:f0)...................... 398 13.1.20lpc_hnbdf ? hpet n bus:device:function (lpc i/f?d31:f0).................... 398 13.1.21lpc_i/o_dec?i/o decode ranges register (lpc i/f?d31:f0) .................. 399 13.1.22lpc_en?lpc i/f enables register (lpc i/f?d31:f0) ............................... 400 13.1.23gen1_dec?lpc i/f generic decode range 1 register (lpc i/f?d31:f0) ................................................................................ 401 13.1.24gen2_dec?lpc i/f generic decode range 2 register (lpc i/f?d31:f0) ................................................................................ 401 http://www..net/ datasheet pdf - http://www..net/ 10 datasheet 13.1.25gen3_dec?lpc i/f generic decode range 3 register (lpc i/f?d31:f0) ................................................................................ 402 13.1.26gen4_dec?lpc i/f generic decode range 4 register (lpc i/f?d31:f0) ................................................................................ 403 13.1.27lgmr ? lpc i/f generic memory range (lpc i/f?d31:f0) (corporate only) .................................................................................. 403 13.1.28fwh_sel1?firmware hub select 1 register (lpc i/f?d31:f0) .................. 404 13.1.29fwh_sel2?firmware hub select 2 register (lpc i/f?d31:f0) .................. 405 13.1.30fwh_dec_en1?firmware hub decode enable register (lpc i/f?d31:f0) ................................................................................ 406 13.1.31bios_cntl?bios control register (lpc i/f?d31:f0) .............................. 408 13.1.32fdcap?feature detection capability id (lpc i/f?d31:f0) ........................ 409 13.1.33fdlen?feature detection capability leng th (lpc i/f?d31:f0) . ........... ...... 409 13.1.34 fdver?feature detection version (lpc i/f?d31:f0) ............................... 409 13.1.35fdvct?feature vector (lpc i/f?d31:f0) ............................................... 410 13.1.36rcba?root complex base address register (lpc i/f?d31:f0) .................. 410 13.2 dma i/o registers (lpc i/f?d31:f0)................................................................. 411 13.2.1 dmabase_ca?dma base and current address registers (lpc i/f?d31:f0)................................................................... 412 13.2.2 dmabase_cc?dma base and current count registers (lpc i/f?d31:f0) ................................................................................ 413 13.2.3 dmamem_lp?dma memory low page registers (lpc i/f?d31:f0) ................................................................................ 413 13.2.4 dmacmd?dma command register (lpc i/f?d31:f0) .............................. 414 13.2.5 dmasta?dma status register (lpc i/f?d31:f0) .................................... 414 13.2.6 dma_wrsmsk?dma write single mask register (lpc i/f?d31:f0) ................................................................................ 415 13.2.7 dmach_mode?dma channel mode register (lpc i/f?d31:f0) ................................................................................ 416 13.2.8 dma clear byte pointer register (lpc i/f?d31:f0)................................... 417 13.2.9 dma master clear register (lpc i/f?d31:f0) .......................................... 417 13.2.10dma_clmsk?dma clear mask register (lpc i/f?d31:f0) ........................ 417 13.2.11dma_wrmsk?dma write all mask register (lpc i/f?d31:f0) ................................................................................ 418 13.3 timer i/o registers (lpc i/f?d31:f0) ............................................................... 419 13.3.1 tcw?timer control word register (lpc i/f?d31:f0) ............................... 420 13.3.2 sbyte_fmt?interval timer status byte format register (lpc i/f?d31:f0) ................................................................................ 422 13.3.3 counter access ports register (lpc i/f?d31:f0) ...................................... 423 13.4 8259 interrupt controller (pic) registers (lpc i/f?d31:f0) ........................................................................................... 424 13.4.1 interrupt controller i/o map (lpc i/f?d31:f0) ........................................ 424 13.4.2 icw1?initialization command word 1 register (lpc i/f?d31:f0) ................................................................................ 425 13.4.3 icw2?initialization command word 2 register (lpc i/f?d31:f0) ................................................................................ 426 13.4.4 icw3?master controller initialization command word 3 register (lpc i/f?d31:f0) ......................................................... 427 13.4.5 icw3?slave controlle r initialization command word 3 register (lpc i/f?d31:f0) ......................................................... 427 13.4.6 icw4?initialization command word 4 register (lpc i/f?d31:f0) ................................................................................ 428 13.4.7 ocw1?operational control word 1 (interrupt mask) register (lpc i/f?d31:f0) .................................................................... 428 13.4.8 ocw2?operational control word 2 register (lpc i/f?d31:f0) ................................................................................ 429 13.4.9 ocw3?operational control word 3 register (lpc i/f?d31:f0) ................................................................................ 430 13.4.10elcr1?master controller edge/level triggered register (lpc i/f?d31:f0) ................................................................................ 431 13.4.11elcr2?slave controller edge/level triggered register (lpc i/f?d31:f0) ................................................................................ 432 13.5 advanced programmable interrupt controller (apic)(d31:f0)................................ 433 13.5.1 apic register map (lpc i/f?d31:f0)...................................................... 433 13.5.2 ind?index register (lpc i/f?d31:f0) ................................................... 434 13.5.3 dat?data register (lpc i/f?d31:f0) .................................................... 434 13.5.4 eoir?eoi register (lpc i/f?d31:f0) .................................................... 435 http://www..net/ datasheet pdf - http://www..net/ datasheet 11 13.5.5 id?identification register (lpc i/f?d31:f0) .......................................... 436 13.5.6 ver?version register (lpc i/f?d31:f0) ................................................ 436 13.5.7 redir_tbl?redirection table (lpc i/f?d 31:f0)..................................... 437 13.6 real time clock registers................................................................................. 439 13.6.1 i/o register address map ...................................................................... 439 13.6.2 indexed registers ................................................................................ 440 13.7 processor interface registers (lpc i/f?d31:f0) ................................................. 444 13.7.1 nmi_sc?nmi status and control register (lpc i/f?d31:f0) ................................................................................ 444 13.7.2 nmi_en?nmi enable (and real time clock index) register (lpc i/f?d31:f0).................................................................... 445 13.7.3 port92?fast a20 and init register (lpc i/f?d31:f0) ............................. 445 13.7.4 coproc_err?coprocessor error register (lpc i/f?d31:f0) ................................................................................ 446 13.7.5 rst_cnt?reset control register (lpc i/f?d31:f0) ................................ 446 13.8 power management registers (pm?d31:f0) ....................................................... 447 13.8.1 power management pci configuration registers (pm?d31:f0) ...................................................................................... 447 13.8.2 apm i/o decode................................................................................... 460 13.8.3 power management i/o registers ........................................................... 461 13.9 system management tco registers (d31:f0) ..................................................... 483 13.9.1 tco_rld?tco timer reload and current value register .......................... 483 13.9.2 tco_dat_in?tco data in register ....................................................... 484 13.9.3 tco_dat_out?tco data out register .................................................. 484 13.9.4 tco1_sts?tco1 status register .......................................................... 484 13.9.5 tco2_sts?tco2 status register .......................................................... 486 13.9.6 tco1_cnt?tco1 control register ......................................................... 488 13.9.7 tco2_cnt?tco2 control register ......................................................... 489 13.9.8 tco_message1 and tco_message2 registers ....................................... 489 13.9.9 tco_wdcnt?tco watchdog control register ......................................... 490 13.9.10sw_irq_gen?software irq generation register .................................... 490 13.9.11tco_tmr?tco timer initial value register............................................. 490 13.10 general purpose i/o registers (d31:f0)............................................................. 491 13.10.1gpio_use_sel?gpio use select register .............................................. 492 13.10.2gp_io_sel?gpio input/output select register ....................................... 492 13.10.3gp_lvl?gpio level for input or output register ..................................... 493 13.10.4gpo_blink?gpo blink enable register .................................................. 493 13.10.5gp_ser_blink?gp serial blink ............................................................. 494 13.10.6gp_sb_cmdsts?gp serial blink command status................................... 495 13.10.7gp_sb_data?gp serial blink data ........................................................ 495 13.10.8gpi_inv?gpio signal invert register....... .............................................. 496 13.10.9gpio_use_sel2?gpio use select 2 register .......................................... 497 13.10.10gp_io_sel2?gpio input/output select 2 register ................................. 498 13.10.11gp_lvl2?gpio level for input or output 2 register ............................... 498 13.10.12gpio_use_sel3?gpio use select 3 regi ster (corporate only) ................ 499 13.10.13gp_io_sel3?gpio input/output select 3 register (corporate only)......... 499 13.10.14gp_lvl3?gpio level for input or output 3 register (corporate only)....... 500 13.10.15gp_rst_sel ? gpio reset select ........................................................ 500 14 sata controller registers (d31:f2) ....................................................................... 501 14.1 pci configuration registers (sata?d31:f2)........................................................ 501 14.1.1 vid?vendor identification register (sata?d31:f2) ................................ 503 14.1.2 did?device identification register (sata?d31:f2) ................................. 503 14.1.3 pcicmd?pci command register (sata?d31:f2)..................................... 503 14.1.4 pcists ? pci status register (sata?d31:f2) ......................................... 504 14.1.5 rid?revision identification register (sata?d31:f2)............................... 505 14.1.6 pi?programming interface register (sata?d31:f2)................................. 505 14.1.7 scc?sub class code register (sata?d31:f2) ........................................ 506 14.1.8 bcc?base class code register (sata?d31:f2) ....................................... 506 14.1.9 pmlt?primary master latency timer register (sata?d31:f2) ................... 507 14.1.10htype?header type (sata?d31:f2) ..................................................... 507 14.1.11pcmd_bar?primary command block base address register (sata?d31:f2) ....................................................................... 507 14.1.12pcnl_bar?primary control block base address register (sata?d31:f2).................................................................................... 508 14.1.13scmd_bar?secondary command block base address register (ide d31:f1) .......................................................................... 508 http://www..net/ datasheet pdf - http://www..net/ 12 datasheet 14.1.14scnl_bar?secondary control block base address register (ide d31:f1) ........................................................................... 508 14.1.15bar ? legacy bus mast er base address register (sata?d31:f2) .................................................................................... 509 14.1.16abar/sidpba1 ? ahci base address register/serial ata index data pair base address (sata?d31:f2) ................................................... 509 14.1.17svid?subsystem vendor identification register (sata?d31:f2) .................................................................................... 510 14.1.18sid?subsystem identification register (sata?d31:f2)............................. 510 14.1.19cap?capabilities pointer register (sata? d31:f2) ......... .......... ........... ...... 510 14.1.20 int_ln?interrupt line register (sata?d3 1:f2)....................................... 511 14.1.21int_pn?interrupt pin register (sata?d31: f2) ........................................ 511 14.1.22ide_tim ? ide timing register (sata?d31:f2) ....................................... 511 14.1.23pid?pci power management capability identification register (sata?d31:f2)........................................................................ 511 14.1.24pc?pci power management capabilities register (sata?d31:f2) .................................................................................... 512 14.1.25pmcs?pci power management control and status register (sata?d31:f2)........................................................................ 512 14.1.26msici?message signaled inte rrupt capability identification (sata?d31:f2) .................................................................................... 513 14.1.27msimc?message signaled interrupt message control (sata?d31:f2) ......... 514 14.1.28msima? message signaled interrupt message address (sata?d31:f2) ....... 515 14.1.29msimd?message signaled interrupt message data (sata?d31:f2) ............ 515 14.1.30map?address map register (sata?d31:f2)............................................. 516 14.1.31pcs?port control and status register (sata?d31:f2) .............................. 516 14.1.32sclkcg?sata clock gating control register........................................... 519 14.1.33sclkgc?sata clock general configuration register................................. 520 14.1.34flrcid?flr capability id (sata?d31:f2) ... ................ .......... ........... ...... 522 14.1.35flrclv?flr capability length and vers ion (sata?d31:f2)..... ............ ...... 522 14.1.36flrc?flr control (sata?d31:f2) ......................................................... 523 14.1.37atc?apm trapping control register (sata?d31:f2)................................. 523 14.1.38ats?apm trapping status register (sata?d31:f2).................................. 524 14.1.39sp scratch pad register (sata?d31:f2) .................................................. 524 14.1.40bfcs?bist fis control/status register (sata?d31:f2) ........................... 525 14.1.41bftd1?bist fis transmit data1 register (sata?d31:f2) ........................ 527 14.1.42bftd2?bist fis transmit data2 register (sata?d31:f2) ........................ 527 14.2 bus master ide i/o registers (d31:f2)............................................................... 528 14.2.1 bmic[p,s]?bus master ide command register (d31:f2) .......................... 529 14.2.2 bmis[p,s]?bus master ide status regist er (d31:f2)................................ 530 14.2.3 bmid[p,s]?bus master ide descriptor table pointer register (d31:f2)................................................................................. 531 14.2.4 air?ahci index register (d31:f2) ........................................................ 531 14.2.5 aidr?ahci index data register (d31:f2)............................................... 531 14.3 serial ata index/data pair superset registers. .................................................... 532 14.3.1 sindx ? serial ata index (d31:f2) ........................................................ 532 14.3.2 sdata ? serial ata data (d31:f2) ......................................................... 532 14.4 ahci registers (d31:f2) .................................................................................. 536 14.4.1 ahci generic host control registers (d31:f2).......................................... 537 14.4.2 vendor specific registers (d31:f2) ......................................................... 545 14.4.3 port registers (d31:f2) ......................................................................... 545 15 sata controller registers (d31:f5) ....................................................................... 563 15.1 pci configuration registers (sata?d31:f5) ........................................................ 563 15.1.1 vid?vendor identification register (sata?d31:f5) ................................. 564 15.1.2 did?device identification register (sata?d31:f5) ................................. 565 15.1.3 pcicmd?pci command register (sata?d31:f5) ..................................... 565 15.1.4 pcists ? pci status register (sata?d31:f5) ......................................... 566 15.1.5 rid?revision identification register (sata?d31:f5) ............................... 566 15.1.6 pi?programming interface register (sata?d31:f5) ................................. 567 15.1.7 scc?sub class code register (sata?d31:f5) ......................................... 567 15.1.8 bcc?base class code register (sata?d31:f5)........................................ 567 15.1.9 pmlt?primary master latency timer register (sata?d31:f5) .................................................................................... 568 15.1.10pcmd_bar?primary command block base address register (sata?d31:f5)........................................................................ 568 http://www..net/ datasheet pdf - http://www..net/ datasheet 13 15.1.11pcnl_bar?primary control block base address register (sata?d31:f5).................................................................................... 568 15.1.12scmd_bar?secondary command block base address register (ide d31:f1) .......................................................................... 569 15.1.13scnl_bar?secondary control block base address register (ide d31:f1) .......................................................................... 569 15.1.14bar ? legacy bus master base address register (sata?d31:f5).................................................................................... 570 15.1.15sidpba ? sata index/data pair base address register (sata?d31:f5).................................................................................... 570 15.1.16svid?subsystem vendor identification register (sata?d31:f5).................................................................................... 571 15.1.17sid?subsystem identification register (sata?d31:f5) ............................ 571 15.1.18cap?capabilities pointer re gister (sata?d31:f5)......... .......... ........... ...... 571 15.1.19int_ln?interrupt line register (sata?d31:f5) ...................................... 571 15.1.20int_pn?interrupt pin register (sata?d31:f5)........................................ 571 15.1.21ide_tim ? ide timing register (sata?d31:f5) ...................................... 572 15.1.22pid?pci power manageme nt capability identification register (sata?d31:f5) ....................................................................... 572 15.1.23pc?pci power management capabilities register (sata?d31:f5).................................................................................... 572 15.1.24pmcs?pci power management control and status register (sata?d31:f5) ....................................................................... 573 15.1.25mid?message signal interrupt identifier (sata?d31:f5) (consumer only).................................................................................. 573 15.1.26mc?message signal interrupt message control (sata?d31:f5) (consumer only).................................................................................. 574 15.1.27ma?message signal interrupt message address (sata?d31:f5) (consumer only).................................................................................. 574 15.1.28md?message signal interrupt message data (sata?d31:f5) (consumer only).................................................................................. 574 15.1.29map?address map register (sata?d31:f5)16......................................... 575 15.1.30pcs?port control and status register (sata?d31:f5).............................. 576 15.1.31satacr0? sa ta capability register 0 (sata?d31: f5) ......... ............ ........ 577 15.1.32satacr1? sa ta capability register 1 (sata?d31: f5) ......... ............ ........ 577 15.1.33flrcid? flr capability id (sata?d31:f5) ....... ........... .......... ........... ...... 577 15.1.34flrclv? flr capability length and valu e (sata?d31:f5) ....... ........... ...... 578 15.1.35flrctrl? flr control (sata?d31:f5) ................................................... 578 15.1.36atc?apm trapping control register (sata?d31:f5) ................................ 579 15.1.37atc?apm trapping control (sata?d31:f5) ............................................ 579 15.2 bus master ide i/o registers (d31:f5) .............................................................. 580 15.2.1 bmic[p,s]?bus master ide command register (d31:f5) .......................... 581 15.2.2 bmis[p,s]?bus master ide status register (d31:f5) ............................... 582 15.2.3 bmid[p,s]?bus master ide descriptor table pointer register (d31:f5) ................................................................................ 582 15.3 serial ata index/data pair superset registers ... ................................................. 583 15.3.1 sindx?sata index register (d31:f5) ................................................... 583 15.3.2 sdata?sata index data register (d31:f5)............................................ 583 16 uhci controllers registers .................................................................................... 589 16.1 pci configuration registers (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) ..................... 589 16.1.1 vid?vendor identification register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) ................................................. 590 16.1.2 did?device identification register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) ................................................. 590 16.1.3 pcicmd?pci command register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) ................................................. 591 16.1.4 pcists?pci status register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) ................................................. 592 16.1.5 rid?revision identification register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) ................................................. 592 16.1.6 pi?programming interface register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) ................................................. 593 16.1.7 scc?sub class code register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) ................................................. 593 16.1.8 bcc?base class code register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) ................................................. 593 http://www..net/ datasheet pdf - http://www..net/ 14 datasheet 16.1.9 mlt?master latency timer register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2).................................................. 593 16.1.10headtyp?header type register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2).................................................. 594 16.1.11base?base address register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2).................................................. 594 16.1.12svid ? subsystem vendor identification register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2).................................................. 594 16.1.13sid ? subsystem identification register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2).................................................. 595 16.1.14cap_ptr?capabilities pointer (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2).................................................. 595 16.1.15 int_ln?interrupt line register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2).................................................. 595 16.1.16int_pn?interrupt pin register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2).................................................. 596 16.1.17flrcid?function level reset capability id (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2).................................................. 596 16.1.18flrncp?function level reset next capability pointer (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2).................................................. 596 16.1.19flrclv?function level rese t capability length and version (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2).................................................. 597 16.1.20usb_flrctrl?flr control register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2).................................................. 597 16.1.21 usb_flrstat?flr status register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2).................................................. 598 16.1.22usb_relnum?serial bus release number register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2).................................................. 598 16.1.23usb_legkey?usb legacy keyboard/mouse control register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) ..................................... 598 16.1.24 usb_res?usb resume enable register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2).................................................. 600 16.1.25cwp?core well policy register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2).................................................. 601 16.1.26ucr1?uchi configuration register 1 (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2).................................................. 601 16.2 usb i/o registers............................................................................................ 602 16.2.1 usbcmd?usb command register .......................................................... 603 16.2.2 usbsts?usb status register ................................................................ 606 16.2.3 usbintr?usb interrupt enable register................................................. 607 16.2.4 frnum?frame number register ............................................................ 607 16.2.5 frbaseadd?frame list base address register........................................ 608 16.2.6 sofmod?start of frame modify register ................................................ 608 16.2.7 portsc[0,1]?port status and control register ........................................ 609 17 ehci controller registers (d29:f7, d26:f7) ........................................................... 611 17.1 usb ehci configuration registers (usb ehci?d29:f7, d26:f7)............................ 611 17.1.1 vid?vendor identification register (usb ehci?d29:f7, d26:f7)................................................................. 612 17.1.2 did?device identification register (usb ehci?d29:f7, d26:f7)................................................................. 612 17.1.3 pcicmd?pci command register (usb ehci?d29:f7, d26:f7)................................................................. 613 17.1.4 pcists?pci status register (usb ehci?d29:f7, d26:f7) ........................ 614 17.1.5 rid?revision identification register (usb ehci?d29:f7, d26:f7)................................................................. 615 17.1.6 pi?programming interface register (usb ehci?d29:f7, d26:f7)................................................................. 615 17.1.7 scc?sub class code register (usb ehci?d29:f7, d26:f7)................................................................. 615 17.1.8 bcc?base class code register (usb ehci?d29:f7, d26:f7)................................................................. 615 17.1.9 pmlt?primary master latency timer register (usb ehci?d29:f7, d26:f7)................................................................. 616 17.1.10mem_base?memory base address register (usb ehci?d29:f7, d26:f7)................................................................. 616 http://www..net/ datasheet pdf - http://www..net/ datasheet 15 17.1.11svid?usb ehci subsystem vendor id register (usb ehci?d29:f7, d26:f7) ................................................................ 616 17.1.12sid?usb ehci subsystem id register (usb ehci?d29:f7, d26:f7) ................................................................ 617 17.1.13cap_ptr?capabilities pointer register (usb ehci?d29:f7, d26:f7) ................................................................ 617 17.1.14int_ln?interrupt line register (usb ehci?d29:f7, d26:f7) ................................................................ 617 17.1.15int_pn?interrupt pin register (usb ehci?d29:f7, d26:f7) ................................................................ 617 17.1.16pwr_capid?pci power management capability id register (usb ehci?d29:f7, d26:f7) .................................................... 618 17.1.17nxt_ptr1?next item pointer #1 register (usb ehci?d29:f7, d26:f7) ................................................................ 618 17.1.18pwr_cap?power management capabilities register (usb ehci?d29:f7, d26:f7) ................................................................ 619 17.1.19pwr_cntl_sts?power management control/ status register (usb ehci?d29:f7, d26:f7) .......................................... 620 17.1.20debug_capid?debug port capability id register (usb ehci?d29:f7, d26:f7) ................................................................ 621 17.1.21nxt_ptr2?next item pointer #2 register (usb ehci?d29:f7, d26:f7) ................................................................ 621 17.1.22debug_base?debug port base offset register (usb ehci?d29:f7, d26:f7) ................................................................ 621 17.1.23usb_relnum?usb release number register (usb ehci?d29:f7, d26:f7) ................................................................ 621 17.1.24fl_adj?frame length adjustment register (usb ehci?d29:f7, d26:f7) ................................................................ 622 17.1.25pwake_cap?port wa ke capability register (usb ehci?d29:f7, d26:f7) ................................................................ 623 17.1.26leg_ext_cap?usb ehci legacy support extended capability register (usb ehci?d29:f7, d26: f7) ............ .......... ........... .... 624 17.1.27leg_ext_cs?usb ehci legacy support extended control / status register (usb ehci?d29:f7, d26:f7) ............................. 624 17.1.28special_smi?intel specific usb 2.0 smi register (usb ehci?d29:f7, d26:f7) ................................................................ 626 17.1.29access_cntl?access control register (usb ehci?d29:f7, d26:f7) ................................................................ 628 17.1.30ehciir1?ehci initialization register 1 (usb ehci?d29:f7, d26:f7) ................................................................ 628 17.1.31flr_cid?function level reset capability id (usb ehci?d29:f7, d26:f7) ................................................................ 628 17.1.32flr_next?function level reset next capability pointer (usb ehci?d29:f7, d26:f7) ................................................................ 629 17.1.33flr_clv?function level rese t capability length and version (usb ehci?d29:f7, d26:f7) ................................................................ 629 17.1.34flr_ctrl?function level reset control register (usb ehci?d29:f7, d26:f7) ................................................................ 630 17.1.35flr_sts?function level reset status register (usb ehci?d29:f7, d26:f7) ................................................................ 630 17.1.36ehciir2?ehci initialization register 2 (usb ehci?d29:f7, d26:f7) ................................................................ 630 17.2 memory-mapped i/o registers .......................................................................... 631 17.2.1 host controller capability registers .......... ............ ........... ........... ............ 631 17.2.2 host controller operational registers ........ .............................................. 635 17.2.3 usb 2.0-based debug port register........................................................ 649 18 intel ? high definition audio co ntroller registers (d27:f0) ................................... 653 18.1 intel ? high definition audio pci configuration space (intel ? high definition audio? d27:f0) ............................................................. 653 18.1.1 vid?vendor identification register (intel ? high definition audio controller?d27:f0)..................................... 655 18.1.2 did?device identification register (intel ? high definition audio controller?d27:f0)..................................... 655 18.1.3 pcicmd?pci command register (intel ? high definition audio controller?d27:f0)..................................... 655 http://www..net/ datasheet pdf - http://www..net/ 16 datasheet 18.1.4 pcists?pci status register (intel ? high definition audio controller?d27:f0) ..................................... 656 18.1.5 rid?revision identification register (intel ? high definition audio controller?d27:f0) ..................................... 657 18.1.6 pi?programming interface register (intel ? high definition audio controller?d27:f0) ..................................... 657 18.1.7 scc?sub class code register (intel ? high definition audio controller?d27:f0) ..................................... 657 18.1.8 bcc?base class code register (intel ? high definition audio controller?d27:f0) ..................................... 657 18.1.9 cls?cache line size register (intel ? high definition audio controller?d27:f0) ..................................... 657 18.1.10lt?latency timer register (intel ? high definition audio controller?d27:f0) ..................................... 658 18.1.11headtyp?header type register (intel ? high definition audio controller?d27:f0) ..................................... 658 18.1.12 hdbarl?intel ? high definition audio lower base address register (intel ? high definition audio?d27:f0).................................................... 658 18.1.13 hdbaru?intel ? high definition audio upper base address register (intel ? high definition audio controller?d27:f0) ..................................... 658 18.1.14svid?subsystem vendor identification register (intel ? high definition audio controller?d27:f0) ..................................... 659 18.1.15sid?subsystem identification register (intel ? high definition audio controller?d27:f0) ..................................... 659 18.1.16capptr?capabilities pointer register (intel ? high definition audio controller?d27:f0) ..................................... 659 18.1.17intln?interrupt line register (intel ? high definition audio controller?d27:f0) ..................................... 660 18.1.18intpn?interrupt pin register (intel ? high definition audio controller?d27:f0) ..................................... 660 18.1.19 hdctl?intel ? high definition audio control register (intel ? high definition audio controller?d27:f0) ..................................... 660 18.1.20tcsel?traffic class select register (intel ? high definition audio controller?d27:f0) ..................................... 661 18.1.21pid?pci power management capability id register (intel ? high definition audio controller?d27:f0) ..................................... 661 18.1.22pc?power management capabilities register (intel ? high definition audio controller?d27:f0) ..................................... 662 18.1.23pcs?power management control and status register (intel ? high definition audio controller?d27:f0) ..................................... 663 18.1.24mid?msi capability id register (intel ? high definition audio controller?d27:f0) ..................................... 664 18.1.25mmc?msi message control register (intel ? high definition audio controller?d27:f0) ..................................... 664 18.1.26mmla?msi message lo wer address register (intel ? high definition audio controller?d27:f0) ..................................... 664 18.1.27mmua?msi message up per address register (intel ? high definition audio controller?d27:f0) ..................................... 664 18.1.28mmd?msi message data register (intel ? high definition audio controller?d27:f0) ..................................... 665 18.1.29pxid?pci express* capability id register (intel ? high definition audio controller?d27:f0) ..................................... 665 18.1.30pxc?pci express* capabilities register (intel ? high definition audio controller?d27:f0) ..................................... 665 18.1.31devcap?device ca pabilities register (intel ? high definition audio controller?d27:f0) ..................................... 666 18.1.32devc?device control register (intel ? high definition audio controller?d27:f0) ..................................... 667 18.1.33devs?device status register (intel ? high definition audio controller?d27:f0) ..................................... 668 18.1.34vccap?virtual channel enhanced capability header (intel ? high definition audio controller?d27:f0) ..................................... 668 18.1.35pvccap1?port vc capability register 1 (intel ? high definition audio controller?d27:f0) ..................................... 669 18.1.36pvccap2 ? port vc capability register 2 (intel ? high definition audio controller?d27:f0) ..................................... 669 http://www..net/ datasheet pdf - http://www..net/ datasheet 17 18.1.37pvcctl ? port vc control register (intel ? high definition audio controller?d27:f0)..................................... 669 18.1.38pvcsts?port vc status register (intel ? high definition audio controller?d27:f0)..................................... 670 18.1.39vc0cap?vc0 resource capability register (intel ? high definition audio controller?d27:f0)..................................... 670 18.1.40vc0ctl?vc0 resource control register (intel ? high definition audio controller?d27:f0)..................................... 671 18.1.41vc0sts?vc0 resource status register (intel ? high definition audio controller?d27:f0)..................................... 671 18.1.42vcicap?vci resource capability register (intel ? high definition audio controller?d27:f0)..................................... 672 18.1.43vcictl?vci resource control register (intel ? high definition audio controller?d27:f0)..................................... 672 18.1.44vcists?vci resource status register (intel ? high definition audio controller?d27:f0)..................................... 673 18.1.45rccap?root complex link declaration enhanced capability header register (intel ? high definition audio cont roller?d27:f0).............. 673 18.1.46esd?element self description register (intel ? high definition audio controller?d27:f0)..................................... 673 18.1.47l1desc?link 1 description register (intel ? high definition audio controller?d27:f0)..................................... 674 18.1.48l1addl?link 1 lower address register (intel ? high definition audio controller?d27:f0)..................................... 674 18.1.49l1addu?link 1 upper address register (intel ? high definition audio controller?d27:f0)..................................... 674 18.2 intel ? high definition audio memory mapped configuration registers (intel ? high definition audio? d27:f0) ............................................................. 675 18.2.1 gcap?global capabilities register (intel ? high definition audio controller?d27:f0)..................................... 679 18.2.2 vmin?minor version register (intel ? high definition audio controller?d27:f0)..................................... 679 18.2.3 vmaj?major version register (intel ? high definition audio controller?d27:f0)..................................... 679 18.2.4 outpay?output payload capability register (intel ? high definition audio controller?d27:f0)..................................... 680 18.2.5 inpay?input payload capability register (intel ? high definition audio controller?d27:f0)..................................... 680 18.2.6 gctl?global control register (intel ? high definition audio controller?d27:f0)..................................... 681 18.2.7 wakeen?wake enable register (intel ? high definition audio controller?d27:f0)..................................... 682 18.2.8 statests?state change status register (intel ? high definition audio controller?d27:f0)..................................... 682 18.2.9 gsts?global status register (intel ? high definition audio controller?d27:f0)..................................... 683 18.2.10outstrmpay?output stream payload capability (intel ? high definition audio controller?d27:f0)..................................... 683 18.2.11instrmpay? input stream payload capability (intel ? high definition audio controller?d27:f0)..................................... 684 18.2.12intctl?interrupt control register (intel ? high definition audio controller?d27:f0)..................................... 685 18.2.13intsts?interrupt status register (intel ? high definition audio controller?d27:f0)..................................... 686 18.2.14walclk?wall clock counter register (intel ? high definition audio controller?d27:f0)..................................... 686 18.2.15ssync?stream synchronization register (intel ? high definition audio controller?d27:f0)..................................... 687 18.2.16corblbase?corb lower base address register (intel ? high definition audio controller?d27:f0)..................................... 687 18.2.17corbubase?corb upper base address register (intel ? high definition audio controller?d27:f0)..................................... 688 18.2.18corbwp?corb write pointer register (intel ? high definition audio controller?d27:f0)..................................... 688 18.2.19corbrp?corb read pointer register (intel ? high definition audio controller?d27:f0)..................................... 688 http://www..net/ datasheet pdf - http://www..net/ 18 datasheet 18.2.20corbctl?corb control register (intel ? high definition audio controller?d27:f0) ..................................... 689 18.2.21corbst?corb status register (intel ? high definition audio controller?d27:f0) ..................................... 689 18.2.22corbsize?corb size register intel ? high definition audio controller?d27:f0) ...................................... 689 18.2.23rirblbase?rirb lower base address register (intel ? high definition audio controller?d27:f0) ..................................... 690 18.2.24rirbubase?rirb upper base address register (intel ? high definition audio controller?d27:f0) ..................................... 690 18.2.25rirbwp?rirb write pointer register (intel ? high definition audio controller?d27:f0) ..................................... 690 18.2.26rintcnt?response interrupt count register (intel ? high definition audio controller?d27:f0) ..................................... 691 18.2.27rirbctl?rirb control register (intel ? high definition audio controller?d27:f0) ..................................... 691 18.2.28rirbsts?rirb status register (intel ? high definition audio controller?d27:f0) ..................................... 692 18.2.29rirbsize?rirb size register (intel ? high definition audio controller?d27:f0) ..................................... 692 18.2.30ic?immediate command register (intel ? high definition audio controller?d27:f0) ..................................... 692 18.2.31ir?immediate response register (intel ? high definition audio controller?d27:f0) ..................................... 693 18.2.32irs?immediate command status register (intel ? high definition audio controller?d27:f0) ..................................... 693 18.2.33dplbase?dma position lower base address register (intel ? high definition audio controller?d27:f0) ..................................... 694 18.2.34dpubase?dma position upper base address register (intel ? high definition audio controller?d27:f0) ..................................... 694 18.2.35sdctl?stream descriptor control register (intel ? high definition audio controller?d27:f0) ..................................... 695 18.2.36sdsts?stream descriptor status register (intel ? high definition audio controller?d27:f0) ..................................... 697 18.2.37sdlpib?stream descriptor link position in buffer register (intel ? high definition audio controller?d27:f0) ......................... 698 18.2.38sdcbl?stream descriptor cyclic buffer length register (intel ? high definition audio controller?d27:f0) ..................................... 698 18.2.39sdlvi?stream descriptor last valid index register (intel ? high definition audio controller?d27:f0) ..................................... 699 18.2.40sdfifow?stream descriptor fifo watermark register (intel ? high definition audio controller?d27:f0) ..................................... 699 18.2.41sdfifos?stream descriptor fifo size register (intel ? high definition audio controller?d27:f0) ..................................... 700 18.2.42sdfmt?stream descriptor format register (intel ? high definition audio controller?d27:f0) ..................................... 701 18.2.43sdbdpl?stream descriptor buff er descriptor list pointer lower base address register (intel ? high definition audio controller?d27:f0) ..... 702 18.2.44sdbdpu?stream descriptor buffer descriptor list pointer upper base address register (intel ? high definition audio controller?d27:f0) ............. 702 19 smbus controller registers (d31:f3) ..................................................................... 703 19.1 pci configuration registers (smbus?d31:f3) ..................................................... 703 19.1.1 vid?vendor identification register (smbus?d31:f3) ............................... 703 19.1.2 did?device identification register (smb us?d31:f3) ............................... 704 19.1.3 pcicmd?pci command register (smbus?d31:f3) .................................. 704 19.1.4 pcists?pci status register (smbus?d31:f3) ........................................ 705 19.1.5 rid?revision identification register (s mbus?d31:f3) ............................. 705 19.1.6 pi?programming interface register (smbus?d31:f3) .............................. 706 19.1.7 scc?sub class code register (smbus?d31:f3) ...................................... 706 19.1.8 bcc?base class code register (smbus?d31:f3)..................................... 706 19.1.9 smbmbar0?d31_f3_smbus memory base address 0 (smbus?d31:f3) ................................................................................. 706 19.1.10smbmbar1?d31_f3_smbus memory base address 1 (smbus?d31:f3) ................................................................................. 707 19.1.11smb_base?smbus base address register (smbus?d31:f3) ................................................................................. 707 http://www..net/ datasheet pdf - http://www..net/ datasheet 19 19.1.12svid?subsystem vendor identification register (smbus?d31:f2/f4) ............................................................................ 707 19.1.13sid?subsystem identification register (smbus?d31:f2/f4)..................... 708 19.1.14int_ln?interrupt line register (smbus?d31:f3) ................................... 708 19.1.15int_pn?interrupt pin register (smbus?d31:f3)..................................... 708 19.1.16hostc?host configuration register (smbus?d31:f3) ............................. 709 19.2 smbus i/o and memory mapped i/o registers .................................................... 710 19.2.1 hst_sts?host status register (smbus?d31:f3).................................... 711 19.2.2 hst_cnt?host control register (smbus?d31:f3) .................................. 712 19.2.3 hst_cmd?host command register (smbus?d31:f3).............................. 714 19.2.4 xmit_slva?transmit slave address register (smbus?d31:f3) ................ 714 19.2.5 hst_d0?host data 0 register (smbus?d31:f3) ..................................... 714 19.2.6 hst_d1?host data 1 register (smbus?d31:f3) ..................................... 714 19.2.7 host_block_db?host block data byte register (smbus?d31:f3) ............ 715 19.2.8 pec?packet error check (pec) register (smbus?d31:f3) ........................ 715 19.2.9 rcv_slva?receive slave address register (smbus?d31:f3) ................... 716 19.2.10slv_data?receive slave data register (smbus?d31:f3) ....................... 716 19.2.11aux_sts?auxiliary status register (smbus?d31:f3) ..... .......... ........... .... 716 19.2.12aux_ctl?auxiliary control register (smbus?d31:f3) . ................ ............ 717 19.2.13smlink_pin_ctl?smlink pin control register (smbus?d31:f3) .............. 717 19.2.14smbus_pin_ctl?smbus pin control register (smbus?d31:f3)................. 718 19.2.15slv_sts?slave status register (smbus?d 31:f3)................................... 718 19.2.16slv_cmd?slave command register (smbus?d31:f3)............................. 719 19.2.17 notify_daddr?notify device address register (smbus?d31:f3) ............ 719 19.2.18notify_dlow?notify data low byte register (smbus?d31:f3) ............... 720 19.2.19notify_dhigh?notify data high byte register (smbus?d31:f3) ............. 720 20 pci express* conf iguration registers .................................................................... 721 20.1 pci express* configuration registers (pci express?d28:f0/f1/f2/f3/f4/f5) ......... 721 20.1.1 vid?vendor identification register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 724 20.1.2 did?device identification register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 724 20.1.3 pcicmd?pci command register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 725 20.1.4 pcists?pci status register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 726 20.1.5 rid?revision identification register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 727 20.1.6 pi?programming interface register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 727 20.1.7 scc?sub class code register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 727 20.1.8 bcc?base class code register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 727 20.1.9 cls?cache line size register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 728 20.1.10plt?primary latency timer register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 728 20.1.11headtyp?header type register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 728 20.1.12bnum?bus number register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 728 20.1.13 slt?secondary latency timer (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 729 20.1.14iobl?i/o base and limit register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 729 20.1.15ssts?secondary status register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 730 20.1.16mbl?memory base and limit register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 731 20.1.17pmbl?prefetchable memory base and limit register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 731 20.1.18pmbu32?prefetchable memory base upper 32 bits register (pci express?d28:f0/f1/f2/f3/f4/f5) ...................................... 731 20.1.19pmlu32?prefetchable memory limit upper 32 bits register (pci express?d28:f0/f1/f2/f3/f4/f5) ...................................... 732 http://www..net/ datasheet pdf - http://www..net/ 20 datasheet 20.1.20capp?capabilities list pointer register (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 732 20.1.21intr?interrupt information register (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 732 20.1.22bctrl?bridge control register (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 733 20.1.23clist?capabilities list register (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 734 20.1.24xcap?pci express* capabilities register (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 734 20.1.25dcap?device capabilities register (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 735 20.1.26dctl?device control register (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 736 20.1.27dsts?device status register (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 737 20.1.28lcap?link capabilities register (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 738 20.1.29lctl?link control register (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 740 20.1.30lsts?link status register (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 741 20.1.31slcap?slot capabilities register (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 742 20.1.32slctl?slot control register (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 743 20.1.33slsts?slot status register (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 744 20.1.34rctl?root control register (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 745 20.1.35rsts?root status register (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 745 20.1.36dcap2?device capabilities 2 register (corporate only) (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 746 20.1.37dctl2?device control 2 register (corporate only) (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 746 20.1.38lctl2?link control 2 register (corporate only) (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 747 20.1.39mid?message signaled interrupt identifiers register (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 747 20.1.40mc?message signaled interrupt message control register (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 747 20.1.41ma?message signaled interrupt message address register (pci express?d28:f0/f1/f2/f3/f4/f5)....................................... 748 20.1.42md?message signaled interrupt message data register (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 748 20.1.43svcap?subsystem ve ndor capability register (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 748 20.1.44svid?subsystem vendor identification register (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 748 20.1.45pmcap?power management capability register (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 749 20.1.46pmc?pci power management capabilities register (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 749 20.1.47pmcs?pci power management control and status register (pci express?d28:f0/f1/f2/f3/f4/f5)....................................... 750 20.1.48mpc2?miscellaneous port configuration register 2 (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 751 20.1.49mpc?miscellaneous port configuration register (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 752 20.1.50smscs?smi/sci status register (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 754 20.1.51rpdcgen?root port dynamic clock gating enable (pci express-d28:f0/f1/f2/f3/f4/f5)..................................................... 755 20.1.52pecr1?pci express* configuration register 1 (pci express?d28:f0/f1/f2/f3/f4/f5) ................................................... 755 http://www..net/ datasheet pdf - http://www..net/ datasheet 21 20.1.53vch?virtual channel ca pability header register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 756 20.1.54vcap2?virtual channe l capability 2 register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 756 20.1.55pvc?port virtual channel control register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 756 20.1.56pvs?port virtual channel status register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 757 20.1.57v0cap?virtual channel 0 resource capability register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 757 20.1.58v0ctl?virtual channel 0 resource control register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 758 20.1.59v0sts?virtual channel 0 resource status register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 758 20.1.60ues?uncorrectable error status register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 759 20.1.61uem?uncorrectable error mask (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 760 20.1.62uev ? uncorrectable error severity (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 761 20.1.63ces ? correctable error status register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 762 20.1.64cem ? correctable error mask register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 762 20.1.65aecc ? advanced error capabilities and control register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 763 20.1.66res ? root error status register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 763 20.1.67rctcl ? root complex topology capability list register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 763 20.1.68esd?element self description register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 764 20.1.69uld ? upstream link description register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 764 20.1.70ulba ? upstream link base address register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 765 20.1.71pecr2 ? pci express* configuration register 2 (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 765 20.1.72peetm ? pci express* extended test mode register (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 765 20.1.73pec1 ? pci express* configuration register 1 (pci express?d28:f0/f1/f2/f3/f4/f5)................................................... 766 21 high precision event timer registers .................................................................... 767 21.1 memory mapped registers................................................................................ 767 21.1.1 gcap_id?general capabilities and identi fication register ......................... 769 21.1.2 gen_conf?general configuration register............................................. 770 21.1.3 gintr_sta?general interrupt status regi ster ........................................ 770 21.1.4 main_cnt?main counter value register ................................................ 771 21.1.5 timn_conf?timer n configuration and ca pabilities register .... ........... ...... 772 21.1.6 timn_comp?timer n comparator value register ..................................... 775 22 serial peripheral interface (spi) ........................................................................... 777 22.1 serial peripheral interface memory mapped configuration registers ....................... 777 22.1.1 bfpr ?bios flash primary region register (spi memory mapped configuration registers) ......................................... 779 22.1.2 hsfs?hardware sequencing flash status register (spi memory mapped configuration registers) ......................................... 779 22.1.3 hsfc?hardware sequencing flash control register (spi memory mapped configuration registers) ......................................... 781 22.1.4 faddr?flash address register (spi memory mapped configuration registers) ......................................... 781 22.1.5 fdata0?flash data 0 register (spi memory mapped configuration registers) ......................................... 782 22.1.6 fdatan?flash data [n] register (spi memory mapped configuration registers) ......................................... 782 http://www..net/ datasheet pdf - http://www..net/ 22 datasheet 22.1.7 frap?flash regions access permissions register (spi memory mapped configuration registers).......................................... 783 22.1.8 freg0?flash region 0 (flash descriptor) register (spi memory mapped configuration registers).......................................... 784 22.1.9 freg1?flash region 1 (bios descriptor) register (spi memory mapped configuration registers).......................................... 784 22.1.10freg2?flash region 2 (me) register (spi memory mapped configuration registers).......................................... 785 22.1.11freg3?flash region 3 (gbe) register (spi memory mapped configuration registers).......................................... 785 22.1.12freg4?flash region 4 (platform data) register (spi memory mapped configuration registers).......................................... 786 22.1.13pr0?protected range 0 register (spi memory mapped configuration registers).......................................... 786 22.1.14pr1?protected range 1 register (spi memory mapped configuration registers).......................................... 787 22.1.15pr2?protected range 2 register (spi memory mapped configuration registers).......................................... 788 22.1.16pr3?protected range 3 register (spi memory mapped configuration registers).......................................... 788 22.1.17pr4?protected range 4 register (spi memory mapped configuration registers).......................................... 789 22.1.18ssfs?software sequencing flash status register (spi memory mapped configuration registers).......................................... 790 22.1.19ssfc?software sequencing flash control register (spi memory mapped configuration registers).......................................... 791 22.1.20preop?prefix opcode configuration register (spi memory mapped configuration registers).......................................... 792 22.1.21optype?opcode type configuration register (spi memory mapped configuration registers).......................................... 792 22.1.22opmenu?opcode menu configuration register (spi memory mapped configuration registers).......................................... 793 22.1.23bbar?bios base address configuration register (spi memory mapped configuration registers).......................................... 794 22.1.24fdoc?flash descriptor ob servability control register (spi memory mapped configuration registers).......................................... 794 22.1.25fdod?flash descriptor observability data register (spi memory mapped configuration registers).......................................... 795 22.1.26afc?additional flash control register (spi memory mapped configuration registers).......................................... 795 22.1.27lvscc? host lower vendor spec ific component capabilities register (spi memory mapped configuration registers).......................................... 796 22.1.28uvscc? host upper vendor specific component capabilities register (spi memory mapped configuration registers).......................................... 797 22.1.29fpb ? flash partition boundary (spi memory mapped configuration registers).......................................... 799 22.2 flash descriptor registers................................................................................. 800 22.2.1 flash descriptor content........................................................................ 800 22.2.2 flash descriptor component section ....................................................... 802 22.2.3 flash descriptor region section .............................................................. 805 22.2.4 flash descriptor master section .............................................................. 807 22.2.5 descriptor upper map section................................................................. 810 22.2.6 intel me vendor specific component capa bilities table ........... ......... .......... 810 22.3 oem section ................................................................................................... 815 22.4 gbe spi flash program registers ....................................................................... 815 22.4.1 glfpr ?gigabit lan flash primary region register (gbe lan memory mapped configuration registers) .................................. 816 22.4.2 hsfs?hardware sequencing flash status register (gbe lan memory mapped configuration registers) .................................. 817 22.4.3 hsfc?hardware sequencing flash control register (gbe lan memory mapped configuration registers) .................................. 818 22.4.4 faddr?flash address register (gbe lan memory mapped configuration registers) .................................. 818 22.4.5 fdata0?flash data 0 register (gbe lan memory mapped configuration registers) .................................. 819 22.4.6 frap?flash regions access permissions register (gbe lan memory mapped configuration registers) .................................. 820 http://www..net/ datasheet pdf - http://www..net/ datasheet 23 22.4.7 freg0?flash region 0 (flash descriptor) register (gbe lan memory mapped configuration registers) .................................. 821 22.4.8 freg1?flash region 1 (bios descriptor) register (gbe lan memory mapped configuration registers) .................................. 821 22.4.9 freg2?flash region 2 (me) register (gbe lan memory mapped configuration registers) .................................. 821 22.4.10freg3?flash region 3 (gbe) register (gbe lan memory mapped configuration registers) .................................. 822 22.4.11fpr0?flash protected range 0 register (gbe lan memory mapped configuration registers) .................................. 822 22.4.12fpr1?flash protected range 1 register (gbe lan memory mapped configuration registers) .................................. 823 22.4.13ssfs?software sequencing flash status register (gbe lan memory mapped configuration registers) .................................. 824 22.4.14ssfc?software sequencing flash control register (gbe lan memory mapped configuration registers) .................................. 825 22.4.15preop?prefix opcode configuration register (gbe lan memory mapped configuration registers) .................................. 826 22.4.16optype?opcode type configuration register (gbe lan memory mapped configuration registers) .................................. 826 22.4.17opmenu?opcode menu configuration register (gbe lan memory mapped configuration registers) .................................. 827 23 thermal sensor registers (d31:f6) ....................................................................... 829 23.1 pci bus configuration registers ........................................................................ 829 23.1.1 vid?vendor identification..................................................................... 830 23.1.2 did?device identification ..................................................................... 830 23.1.3 cmd?command .................................................................................. 830 23.1.4 sts?status ........................................................................................ 831 23.1.5 rid?revision identification................................................................... 831 23.1.6 pi? programming interface................................................................... 831 23.1.7 scc?sub class code ........................................................................... 832 23.1.8 bcc?base class code .......................................................................... 832 23.1.9 cls?cache line size............................................................................ 832 23.1.10lt?latency timer................................................................................ 832 23.1.11bist?built-in self test ......................................................................... 833 23.1.12tbar?thermal base ............................................................................ 833 23.1.13tbarh?thermal base high dword......................................................... 833 23.1.14svid?subsystem vendor id ................................................................. 834 23.1.15sid?subsystem id .............................................................................. 834 23.1.16cap_ptr ?capabilities pointer. ................ ............ ........... ........... ............ 834 23.1.17offset 3ch ? intln?interrupt line......................................................... 834 23.1.18intpn?interrupt pin ............................................................................ 835 23.1.19tbarb?bios assigned thermal base address ......................................... 835 23.1.20tbarbh?bios assigned thermal base high dword ................................. 835 23.1.21pid?pci power management capability id .. .......... ........... ........... ............ 836 23.1.22pc?power management capa bilities ......... ............ ........... ........... ............ 836 23.1.23pcs?power management control and status ........................................... 837 23.2 thermal memory mapped configuration registers (thermal sensor - d31:f26) ............................................................................. 838 23.2.1 tsxe?thermal sensor [1:0] enable ....................................................... 838 23.2.2 tsxs?thermal sensor[1:0] status......................................................... 839 23.2.3 tsxttp?thermal sensor [1:0] catastrophic trip point .............................. 839 23.2.4 tsxco?thermal sensor [1:0] catastrophic lock-down............................. 839 23.2.5 tsxpc?thermal sensor [1:0] policy control ............................................ 840 23.2.6 tsxlock?thermal sensor [1:0] register lock control ............................. 840 http://www..net/ datasheet pdf - http://www..net/ 24 datasheet figures 2-1 intel ? ich10 interface signals block diagram..........................................................46 2-1 example external rtc circuit.................................................................................79 4-1 ich10 conceptual system clock diagram ........... .....................................................92 5-1 generation of serr# to platform ...........................................................................99 5-2 lpc interface diagram ........................................................................................ 107 5-3 intel ? ich10 dma controller ............................................................................... 112 5-4 dma request assertion through ldrq# ................................................................ 115 5-5 coprocessor error timing diagram ....................................................................... 140 5-6 tco legacy/compatible mode smbus configuration ................................................ 169 5-7 advanced tco intel ? me smbus/smlink configuration............................................ 171 5-8 advanced tco bmc mode smbus/smlink configuration ........................................... 172 5-9 serial post over gpio reference circuit ................................................................. 174 5-10 sata power states ............................................................................................. 181 5-11 flow for port enable / device present bits.............................................................. 183 5-12 serial data transmitted over the sgpio interfac e ................................................... 188 5-13 usb legacy keyboard flow diagram ..................................................................... 198 5-14 intel ? ich10-usb port connections default six and six configuration...................... 206 5-15 intel ? ich10-usb port connections eight and four configuration ............................ 206 5-16 flash partition boundary .............................. ....................................................... 231 5-17 flash descriptor sections .................................................................................... 232 6-1 intel ? ich10 ballout (top view?left side) ............................................................. 244 6-2 intel ? ich10 ballout (top view?right side) ........................................................... 245 7-1 intel ? ich10 package (top view)......................................................................... 253 7-2 intel ? ich10 package (bottom view).................................................................... 254 7-3 intel ? ich10 package (side view)........................................................................ 254 8-1 clock timing...................................................................................................... 280 8-2 valid delay from rising clock edge ................ ....................................................... 280 8-3 setup and hold times......................................................................................... 281 8-4 float delay........................................................................................................ 281 8-5 pulse width ....................................................................................................... 281 8-6 output enable delay........................................................................................... 281 8-7 usb rise and fall times ...................................................................................... 282 8-8 usb jitter ......................................................................................................... 282 8-9 usb eop width .................................................................................................. 282 8-10 smbus transaction ............................................................................................. 283 8-11 smbus timeout.................................................................................................. 283 8-12 spi timings ....................................................................................................... 284 8-13 intel ? high definition audio input and output timings ............................................ 284 8-14 power sequencing and reset signal timings .......................................................... 285 8-15 g3 (mechanical off) to s0 timings........................................................................ 286 8-16 s0 to s1 to s0 timings ....................................................................................... 287 8-17 s0 to s5 to s0 timings ....................................................................................... 287 8-18 c0 to c2 to c0 timings ....................................................................................... 288 8-19 c0 to c3 to c0 timings ....................................................................................... 288 8-20 c0 to c4 to c0 timings ....................................................................................... 289 8-21 sleep control signal relationship - host b oots and intel management engine off .......... 290 8-22 sleep control signal relationship - host and intel management engine boot after g3 ............................................................................................................ 290 8-23 sleep control signal relationship - host stays in s5 and intel management engine boots after g3 ......................................................................................... 291 8-24 s4, s5/m1 to s0/m0 ........................................................................................... 291 8-25 s0 to s3/s4/s5 and g3 timings ........................................................................... 291 http://www..net/ datasheet pdf - http://www..net/ datasheet 25 tables 1-1 industry specifications ......................................................................................... 33 1-2 pci devices and functions .................................................................................... 37 1-3 intel ? ich10 components .................................................................................... 44 2-1 direct media interface signals ............................................................................... 47 2-2 pci express* signals............................................................................................ 48 2-3 lan connect interface signals ............................................................................... 48 2-4 gigabit lan connect interface signals .................................................................... 49 2-5 firmware hub interface signals ............................................................................. 50 2-6 pci interface signals............................................................................................ 50 2-7 serial ata interface signals .................................................................................. 52 2-8 lpc interface signals ........................................................................................... 55 2-9 interrupt signals ................................................................................................. 55 2-10 usb interface signals........................................................................................... 56 2-11 power management interface signals ..................................................................... 58 2-12 processor interface signals ................................................................................... 61 2-13 smbus interface signals ....................................................................................... 62 2-14 system management interface signals ................................................................... 63 2-15 real time clock interface ..................................................................................... 64 2-16 other clocks ....................................................................................................... 65 2-17 miscellaneous signals ........................................................................................... 65 2-18 intel? high definition audio link signals ....... ......................................................... 66 2-19 serial peripheral interface (spi ) signals.................................................................. 67 2-20 controller link signals.......................................................................................... 68 2-21 intel? quiet system technology signals ................................................................ 68 2-22 jtag signals ....................................................................................................... 69 2-23 general purpose i/o signals.................................................................................. 70 2-24 power and ground signals .................................................................................... 73 2-25 functional strap definitions..... .............................................................................. 75 3-1 integrated pull-up and pull-down resistors ......... .................................................... 81 3-2 power plane and states for output and i/o si gnals for configurations......................... 83 3-3 power plane for input signals for configurations .. .................................................... 88 4-1 intel ? ich10 and system clock domains ................................................................ 91 5-1 pci bridge initiator cycle types............................................................................. 93 5-2 type 1 address format......................................................................................... 96 5-3 msi versus pci irq actions................................................................................... 98 5-4 lan mode support ............................................................................................. 103 5-5 lpc cycle types supported ................................................................................. 108 5-6 start field bit definitions ........................... ......................................................... 108 5-7 cycle type bit definitions ................................................................................... 109 5-8 transfer size bit definition.................................................................................. 109 5-9 sync bit definition ............................................................................................ 110 5-10 dma transfer size ............................................................................................. 114 5-11 address shifting in 16-bit i/o dma transfers......................................................... 114 5-12 counter operating modes ................................................................................... 119 5-13 interrupt controller core connections................................................................... 121 5-14 interrupt status registers................................................................................... 122 5-15 content of interrupt vector byte .......................................................................... 122 5-16 apic interrupt mapping1 .................................................................................... 128 5-17 interrupt message address format....................................................................... 130 5-18 interrupt message data format ........................................................................... 131 5-19 stop frame explanation...................................................................................... 133 5-20 data frame format ............................................................................................ 134 5-21 configuration bits reset by rt crst# assertion ..................................................... 137 5-22 init# going active ............................................................................................ 139 5-23 nmi sources ..................................................................................................... 140 5-24 dp signal differences ......................................................................................... 141 5-25 general power states for systems using intel ? ich10............................................ 143 5-26 state transition rules for intel ? ich10 ................................................................ 144 5-27 system power plane........................................................................................... 145 5-28 causes of smi# and sci ..................................................................................... 146 5-29 break events..................................................................................................... 149 5-30 sleep types ...................................................................................................... 151 5-31 causes of wake events....................................................................................... 152 5-32 gpi wake events ............................................................................................... 153 5-33 transitions due to power failure ..................... ..................................................... 154 http://www..net/ datasheet pdf - http://www..net/ 26 datasheet 5-34 transitions due to power button .......................................................................... 155 5-35 transitions due to ri# signal .............................................................................. 157 5-36 write only registers with read paths in alt access mode........................................ 159 5-37 pic reserved bits return values .......................................................................... 161 5-38 register write accesses in alt access mode .......................................................... 161 5-39 intel ? ich10 clock inputs ................................................................................... 164 5-40 causes of host and global resets ......................................................................... 166 5-41 event transitions that cause messages ................................................................. 170 5-42 multi-activity led message type ........................................................................... 187 5-43 legacy replacement routing ............................................................................... 190 5-44 bits maintained in low power states .............. ....................................................... 197 5-45 usb legacy keyboard state transitions ........... ..................................................... 198 5-46 uhci vs. ehci ................................................................................................... 201 5-47 debug port behavior........................................................................................... 210 5-48 i 2 c block read................................................................................................... 218 5-49 enable for smbalert# ....................................................................................... 221 5-50 enables for smbus slave write and smbus host events ........................................... 221 5-51 enables for the host notify command ................................................................... 221 5-52 slave write registers.......................................................................................... 223 5-53 command types ................................................................................................ 223 5-54 slave read cycle format..................................................................................... 224 5-55 data values for slave read registers............. ....................................................... 225 5-56 host notify format ............................................................................................. 227 5-57 region size versus erase granularity of flas h components ...................................... 231 5-58 region access control table ................................................................................ 233 5-59 hardware sequencing commands and opcode requirements ................................... 236 5-60 flash protection mechanism summary .................................................................. 237 5-61 recommended pinout for 8-pin serial flash device ................................................. 238 5-62 recommended pinout for 16-pin serial flash devi ce ............................................... 239 6-1 intel ? ich10 ballout by signal name ................................................................... 246 8-1 intel ? ich10 absolute maximum ratings............................................................... 255 8-2 dc current characteristics (consumer only)1 ........................................................ 255 8-3 dc current characteristics (corporate only) .......................................................... 257 8-4 dc characteristic input signal association ......... .................................................... 258 8-5 dc input characteristics ..................................................................................... 260 8-6 dc characteristic output signal association ....... .................................................... 262 8-7 dc output characteristics ............................ ....................................................... 264 8-8 other dc characteristics ..................................................................................... 266 8-9 clock timings .................................................................................................... 268 8-10 pci interface timing........................................................................................... 269 8-11 universal serial bus timing ................................................................................. 270 8-12 sata interface timings....................................................................................... 271 8-13 smbus timing.................................................................................................... 272 8-14 intel ? high definition audio timing ...................................................................... 272 8-15 lpc timing ........................................................................................................ 273 8-16 miscellaneous timings......................................................................................... 273 8-17 spi timings (20 mhz) ......................................................................................... 273 8-18 spi timings (33 mhz) ......................................................................................... 274 8-19 sst timings ...................................................................................................... 274 8-20 peci timings ..................................................................................................... 275 8-21 power sequencing and reset signal timings .......................................................... 275 8-22 power management timings ................................................................................ 277 9-1 pci devices and functions................................................................................... 294 9-2 fixed i/o ranges decoded by intel ? ich10 ........................................................... 296 9-3 variable i/o decode ranges ................................................................................ 298 9-4 memory decode ranges from processor perspective ............................................... 299 10-1 chipset configuration register memory map (memory space)................................... 303 11-1 pci bridge register address map (pci-pci?d30:f0)............................................... 355 12-1 gigabit lan configuration registers address map (gigabit lan ?d25:f0)....................................................................................... 371 12-2 gigabit lan base address a registers address map (gigabit lan? d25:f0)....................................................................................... 384 13-1 lpc interface pci register address map (lpc i/f?d31:f0)...................................... 387 13-2 dma registers ................................................................................................... 411 13-3 pic registers (lpc i/f?d31:f0) .......................................................................... 424 13-4 apic direct registers (lpc i/f?d31:f0) ............................................................... 433 13-5 apic indirect registers (lpc i/f?d31:f0)............................................................. 433 http://www..net/ datasheet pdf - http://www..net/ datasheet 27 13-6 rtc i/o registers .............................................................................................. 439 13-7 rtc (standard) ram bank .................................................................................. 440 13-8 processor interface pci register address map (lpc i/f?d31:f0) ............................. 444 13-9 power management pci register address map (pm?d31:f0)................................... 447 13-10 apm register map .............................................................................................. 460 13-11 acpi and legacy i/o register map ....................................................................... 461 13-12 tco i/o register address map............................................................................. 483 13-13 registers to control gpio address map................................................................. 491 14-1 sata controller pci register address map (sata?d31:f2)...................................... 501 14-2 bus master ide i/o register address map ............................................................. 528 14-3 ahci register address map ................................................................................. 536 14-4 generic host controller register address map........................................................ 537 14-5 port [5:0] dma register address map ................................................................... 545 15-1 sata controller pci register address map (sata?d31:f5)...................................... 563 15-2 bus master ide i/o register address map ............................................................. 580 16-1 uhci controller pci configuration map ................................................................. 589 16-2 uhci controller pci register address map (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2)............................................................... 589 16-3 usb i/o registers.............................................................................................. 602 16-4 run/stop, debug bit interaction swdbg (bit 5) , run/stop (bit 0) operation ............. 605 17-1 usb ehci pci register address map (usb ehci?d29:f7, d26:f7) .......................... 611 17-2 enhanced host controller capability registers .. ........... ........... ............ ......... .......... 631 17-3 enhanced host controller operational register address map .................................... 635 17-4 debug port register address map ........................................................................ 649 18-1 intel ? high definition audio pci register address map (intel ? high definition audio d27:f0) .................................................................. 653 18-2 intel ? high definition audio pci register address map (intel ? high definition audio d27:f0) .................................................................. 675 19-1 smbus controller pci register address map (smbus?d31:f3)................................. 703 19-2 smbus i/o and memory mapped i/o register address map...................................... 710 20-1 pci express* configuration registers address map (pci express?d28:f0/f1/f2/f3/f4/f5) ............................................................... 721 21-1 memory-mapped registers .................................................................................. 767 22-1 serial peripheral interface (spi) register address map (spi memory mapped configuration registers)....................................................... 777 22-2 gigabit lan spi flash program register address map (gbe lan memory mapped configuration registers) ............................................... 815 23-1 thermal sensor register address map .................................................................. 829 23-2 thermal memory mapped configuration register address map ................................. 838 http://www..net/ datasheet pdf - http://www..net/ 28 datasheet revision history revision number description revision date -001 ? initial release. june 2008 -002 ? added intel ich10 corporate components ? added notes 12 and 13 to table 2-23, upda ted signal description for vccglan1_5 and vccglan3_3 in table 2-24, and updated gpio 33 and gpio49 strap definitions in table 2-25. ? updated register descriptions for usbir1 (section 10.1.82), us bir2 (section 10.1.83), and ehciir1 (section 17.1.30) september 2008 -003 ? updated intel ich10 corpor ate components table october 2008 http://www..net/ datasheet pdf - http://www..net/ datasheet 29 intel ? ich10 features ? direct media interface ? 10 gb/s each direction, full duplex ? transparent to software ? pci express* ? 6 pci express root ports ? supports pci express 1.1 ? ports 1-4 can be static ally configured as 4x1, or 1x4 ? support for full 2.5 gb/s bandwidth in each direction per x1 lane ? module based hot-pl ug supported (e.g., expresscard*) ? pci bus interface ? supports pci rev 2.3 specification at 33 mhz ? four available pci req/gnt pairs ? support for 64-bit addressing on pci using dac protocol ? integrated serial ata host controller ? up to six sata ports ? data transfer rates up to 3.0 gb/s (300 mb/s). ? integrated ahci controller ? external sata support ? port disable capability ? intel ? matrix storage technology ? configures the ich10 sata controller as a raid controller supporting raid 0/1/5/10 ? intel ? high definition audio interface ? pci express endpoint ? independent bus mast er logic for eight general purpose streams: four input and four output ? support four external codecs ? supports variable le ngth stream slots ? supports multichannel, 32-bit sample depth, 192 khz sample rate output ? provides mic array support ? allows for non-48 khz sampling output ? support for acpi device states ? low voltage mode ? intel ? quiet system technology ? four tach signals and three pwm signals ? improved algorithms fo r better performance ? simple serial transport (sst) 1.0 bus and platform environment co ntrol interface (peci) ? usb 2.0 ? six uhci host controllers, supporting up to twelve external ports ? two ehci host controllers, supporting up to twelve external ports ? two configuration options for ehci controllers 6+6 and 8+4 ? per-port-disable capability ? includes up to two usb 2.0 high-speed debug ports ? supports wake-up from sl eeping states s1-s4 supports legacy ke yboard/mouse software ? integrated gigabit lan controller ? integrated asf management controller ? network security with system defense ? supports ieee 802.3 ? lan connect interface (lci) and gigabit lan connect interface (glci) ? 10/100/1000 mbps ethernet support ? jumbo frame support ? intel ? active management technology with system defense (corporate only) ? network outbreak containment heuristics ? intel ? i/o virtualization (vt-d) support ? intel ? trusted execution technology (intel txt) support (corporate only) ? power management logic ? supports acpi 3.0b ? acpi-defined power states (c1, c2, c3, c4, s1, s3-s5) ? acpi power management timer ? smi# generation ? all registers readable /restorable for proper resume from 0 v suspend states ? support for apm-based legacy power management for non-ac pi implementations ? external glue integration ? integrated pull-up, pull-down and series termination resistors on processor i/f ? integrated pull-down a nd series resistors on usb ? enhanced dma controller ? two cascaded 8237 dma controllers ? supports lpc dma http://www..net/ datasheet pdf - http://www..net/ 30 datasheet note: not all features are available on all ich10 components. see section 1.3 for more details. ? smbus ? faster speed, up to 100 kbps ? flexible smbus/smli nk architecture to optimize for asf ? provides independent manageability bus through smlink interface ? supports smbus 2.0 specification ? host interface allows processor to communicate via smbus ? slave interface allows an internal or external microcontroller to access system resources ? compatible with most two-wire components that are also i 2 c compatible ? high precision event timers ? advanced operating system interrupt scheduling ? timers based on 82c54 ? system timer, refresh request, speaker tone output ? real-time clock ? 256 byte battery-backed cmos ram ? integrated oscill ator components ? lower power dc/dc converter implementation ? system tco reduction circuits ? timers to generate smi# and reset upon detection of system hang ? timers to detect improper processor reset ? integrated processor frequency strap logic ? supports ability to disable external devices ? interrupt controller ? supports up to eight pci interrupt pins ? supports pci 2.3 message signaled interrupts ? two cascaded 82c59 with 15 interrupts ? integrated i/o apic capability with 24 interrupts ? supports processor system bus interrupt delivery ? 1.1 v operation with 1.5 and 3.3 v i/o ? 5 v tolerant buffers on pci, usb and selected legacy signals ? 1.1 v core voltage ? five integrated voltage regulators for different power rails ? firmware hub i/f supports bios memory size up to 8 mbytes ? serial peripheral interface (spi) ? supports up to two spi devices ? supports 20 mhz and 33 mhz spi devices ? new: dual erase support ? low pin count (lpc) i/f ? supports two master/dma devices. ? support for security device (trusted platform module) connected to lpc. ? gpio ? ttl, open-drain, inversion ? gpio lock down ? new: jtag (corporate only) ? boundary scan for testing during board manufacturing ? package 31x31 mm 676 mbga http://www..net/ datasheet pdf - http://www..net/ datasheet 31 intel ? ich10 configuration spi bios spi flash intel ? gigabit ethernet phy intel ? ich10 usb 2.0 (supports 12 usb ports dual ehci controller) system management (tco) gpio smbus 2.0/i 2 c power management pci bus ... clock generators s l o t s l o t intel ? high definition audio codec(s) firmware hub other asics (optional) lpc i/f super i/o sata (6 ports) pci express* x1 dmi (to (g)mch) tpm (optional) lci glci jtag* (corporate only) http://www..net/ datasheet pdf - http://www..net/ 32 datasheet http://www..net/ datasheet pdf - http://www..net/ datasheetcdi / ibl #: 373635 33 introduction 1 introduction this document is intended for original equipment manufacturers and bios vendors creating intel ? i/o controller hub 10 (ich10) family based products. this document is for the following components: consumer family ?intel ? 82801jib ich10 consumer base (ich10) ?intel ? 82801jir ich10 raid (ich10r) corporate family ?intel ? 82801jd ich10 corporate base (ich10d) ?intel ? 82801jdo ich10 digital office (ich10do) section 1.3 provides high-level feature differen ces for the ich10 family components. note: throughout this document, ich10 is used as a general ich10 term and refers to the intel 82801jib ich10, intel 82801jir ich10r, intel 82801jd ich10d, intel 82801jdo ich10do components, unless specifically noted otherwise. note: throughout this document, the term ?consumer only? refers to information that is for the intel 82801jib ich10 and intel 82801jir ich10r, unless specifically noted otherwise. the term ?corporate only? refe rs to information that is for the intel 82801jd ich10d and 82801jdo ich10do, unless specifically noted otherwise. 1.1 about this manual this manual assumes a working knowledge of the vocabulary and principles of pci express*, usb, ahci, sata, intel ? high definition audio (intel ? hd audio), smbus, pci, acpi, and lpc. although some details of these features are described within this manual, refer to the individual in dustry specifications listed in ta b l e 1 - 1 for the complete details. table 1-1. industry specifications specification location pci express* base specification, revision 1.1 http://www.pcisig.com/specifications low pin count interface specification, revision 1.1 (lpc) http://developer.intel.com/design/chipsets/ industry/lpc.htm system management bus specification, version 2.0 (smbus) http://www.smbus.org/specs/ pci local bus specification, revision 2.3 (pci) http://www.pcisig.com/specifications pci power management specification, revision 1.1 http://www.pcisig.com/specifications universal serial bus specification (usb), revision 2.0 http://www.usb.org/developers/docs advanced configuration and power interface, version 3.0b (acpi) http://www.acpi.info/spec.htm universal host controller interface, revision 1.1 (uhci) http://developer.intel.com/design/usb/ uhci11d.htm http://www..net/ datasheet pdf - http://www..net/ introduction 34 datasheetcdi / ibl #: 373635 enhanced host controller interface specification for universal serial bus, revision 1.0 (ehci) http://developer.intel.com/technology/usb/ ehcispec.htm serial ata specification, revision 2.5 h ttp://www.serialata.org/specifications.asp serial ata ii: extensions to serial ata 1.0, revision 1.0 http://www.serialata.org/specifications.asp serial ata ii cables an d connectors volume 2 gold http://www.serialata.org/specifications.asp alert standard format specification, version 1.03 http://www.dmtf.org/standards/asf ieee 802.3 fast ethernet http://standards.ieee.org/getieee802/ at attachment - 6 with packet interface (ata/ atapi - 6) http://t13.org (t13 1410d) ia-pc hpet (high precision event timers) specification, revision 0.98a http://www.intel.com/hardwaredesign/ hpetspec.htm tpm specification 1.02, level 2 revision 103 http://www.trustedcomputinggroup.org/specs/ tpm intel ? i/o controller hub 10 (ich10) family specification update http://www.intel.com/design/chipsets/ specupdt/319974.pdf intel ? i/o controller hub 10 (ich10) family thermal and mechanical design guidelines http://www.intel.com/design/chipsets/ designex/319975.pdf intel ? ich10 eds spec. update, latest revision intel users: http://esales.intel.com search for ?ich10? external users : http://www.intel.com/ibl chipsets > south bridge s/io controller hub > ich family > ich10 > technical intel ? ich10 chipset mechanical ballout file, latest revision intel ? ich10 family xor chains in-circuit tester package, revision tbd intel ? ich10 ibis model , revision latest revision intel users: http://esales.intel.com search for ?ich10? external users : http://www.intel.com/ibl chipsets > south bridge s/io controller hub > ich family > ich10 > technical table 1-1. industry specifications specificatio nlocation http://www..net/ datasheet pdf - http://www..net/ datasheetcdi / ibl #: 373635 35 introduction chapter 1. introduction chapter 1 introduces the ich10 and provides information on manual organization and gives a general overview of the ich10. chapter 2. signal description chapter 2 provides a block diagram of the ich10 and a detailed description of each signal. signals are arranged according to in terface and details are provided as to the drive characteristics (input/output, open-drain, etc.) of all signals. chapter 3. intel ? ich10 pin states chapter 3 provides a complete list of signals, their associated power well, their logic level in each suspend state, and their logic level before and after reset. chapter 4. intel ? ich10 and system clock domains chapter 4 provides a list of each clock domain associated with the ich10 in an ich10 based system. chapter 5. functional description chapter 5 provides a detailed description of the functions in the ich10. all pci buses, devices and functions in this manual are ab breviated using the following nomenclature; bus:device:function. this manual abbreviates buses as b0 and b1, devices as d8, d27, d28, d29, d30 and d31 and functions as f0, f1, f2, f3, f4, f5, f6 and f7. for example device 31 function 0 is abbreviated as d31:f0, bus 1 device 8 function 0 is abbreviated as b1:d8:f0. generally, the bus number will not be used, and can be considered to be bus 0. note that the ich 10?s external pci bus is typically bus 1, but may be assigned a different number depending upon system configuration. chapter 6. ballout definition chapter 6 provides a table of each signal and its ball assignment in the 676-mbga package. chapter 7. package information chapter 7 provides drawings of the physical dimensions and characteristics of the 676- mbga package. chapter 8. electrical characteristics chapter 8 provides all ac and dc characterist ics including detailed timing diagrams. chapter 9. register and memory mappings chapter 9 provides an overview of the registers, fixed i/o ranges, variable i/o ranges and memory ranges decoded by the ich10. chapter 10. chipset configuration registers chapter 10 provides a detailed description of all registers and base functionality that is related to chipset configuration and not a spec ific interface (such as lpc, pci, or pci express*). it contains the root complex register block, which describes the behavior of the upstream internal link. chapter 11. pci-to-pci bridge registers chapter 11 provides a detailed description of all registers that reside in the pci-to-pci bridge. this bridge resides at device 30, function 0 (d30:f0). chapter 12. integrated lan controller registers chapter 12 provides a detailed description of all registers that reside in the ich10?s integrated lan controller. the integrated la n controller resides at device 25, function 0 (d25:f0). http://www..net/ datasheet pdf - http://www..net/ introduction 36 datasheetcdi / ibl #: 373635 chapter 13. lpc bridge registers chapter 13 provides a detailed description of all re gisters that reside in the lpc bridge. this bridge resides at device 31, function 0 (d31:f0). this function contains registers for many different units within the ich10 in cluding dma, timers, interrupts, processor interface, gpio, power management, system management and rtc. chapter 14. sata controller registers chapter 14 provides a detailed description of a ll registers that reside in the sata controller #1. this controller resides at device 31, function 2 (d31:f2). chapter 15. sata controller registers chapter 15 provides a detailed description of a ll registers that reside in the sata controller #2. this controller resides at device 31, function 5 (d31:f5). chapter 16. uhci controller registers chapter 16 provides a detailed description of all registers that reside in the six uhci host controllers. these controllers reside at device 29, functions 0, 1, 2, and 3 (d29:f0/f1/f2/f3) and device 26, function 0, 1 and 2 (d26:f0/f1/f2). chapter 17. ehci co ntroller registers chapter 17 provides a detailed description of all registers that reside in the two ehci host controllers. these controllers reside at device 29, function 7 (d29:f7) and device 26, function 7 (d26:f7). chapter 18. smbus co ntroller registers chapter 19 provides a detailed description of a ll registers that reside in the smbus controller. this controller resides at device 31, function 3 (d31:f3). chapter 19. intel ? high definition audio controller registers chapter 18 provides a detailed description of a ll registers that reside in the intel high definition audio controller. this controller resides at device 27, function 0 (d27:f0). chapter 20. pci express* port controller registers chapter 20 provides a detailed description of all registers that reside in the pci express controller. this controller resides at device 28, functions 0 to 5 (d30:f0-f5). chapter 21. high precisio n event timers registers chapter 21 provides a detailed description of all re gisters that reside in the multimedia timer memory mapped register space. chapter 22. serial periph eral interface registers chapter 22 provides a detailed description of a ll registers that reside in the spi memory mapped register space. chapter 23. thermal sensors chapter 23 provides a detailed description of all registers that reside in the thermal sensors pci configuration space. the registers reside at device 31, function 6 (d31:f6). http://www..net/ datasheet pdf - http://www..net/ datasheetcdi / ibl #: 373635 37 introduction 1.2 overview the ich10 provides extensive i/o suppor t. functions and capabilities include: ? pci express* base specification, revision 1.1 support ? pci local bus specification , revision 2.3 support for 33 mhz pci operations (supports up to four req/gnt pairs). ? acpi power management logic support, revision 3.0b ? enhanced dma controller, interrupt controller, and timer functions ? integrated serial ata host controllers with independent dma operation on up to six ports. ? usb host interface with support for up to twelve usb ports; six uhci host controllers; two ehci high-speed usb 2.0 host controllers ? integrated 10/100/1000 gigabit ethernet mac with system defense ? system management bus (smbus) specification , version 2.0 with additional support for i 2 c devices ? supports intel ? high definition audio ? supports intel ? matrix storage technology ? supports intel ? active management technology (corporate only) ? supports intel ? virtualization technology for directed i/o ? supports intel ? trusted execution technology (corporate only) ? low pin count (lpc) interface ? firmware hub (fwh) interface support ? serial peripheral interface (spi) support ?intel ? quiet system technology ? integrated tpm 1.2 (corporate only) ? jtag boundary scan support (corporate only) the intel ich10 incorporates a variety of pci devices and functions, as shown in ta b l e 1 - 2 . they are divided into seven logical devices. the first is the dmi-to-pci bridge (device 30). the second device (dev ice 31) contains most of the standard pci functions that always existed in the pci-to -isa bridges (south bridges), such as the intel piix4. the third and fourth (device 29 and device 26) are the usb host controller devices. the fifth (device 28) is pci express device. the sixth (device 27) is the hd audio controller device, and the seventh (device 25) is the gigabit ethernet controller device. table 1-2. pci devices and functions (sheet 1 of 2) bus:device:function function description bus 0:device 30:function 0 dmi-to-pci bridge bus 0:device 31:function 0 lpc controller 1 bus 0:device 31:function 2 sata controller #1 bus 0:device 31:function 5 sata controller #2 3 bus 0:device 31:function 6 thermal subsystem bus 0:device 31:function 3 smbus controller bus 0:device 29:function 0 usb fs/ls uhci controller #1 http://www..net/ datasheet pdf - http://www..net/ introduction 38 datasheetcdi / ibl #: 373635 notes: 1. the pci-to-lpc bridge contai ns registers that control lp c, power manage ment, system management, gpio, proces sor interface, rtc, inte rrupts, timers, and dma 2. device 26:function 2 maybe configured as device 29:function 3 during bios post. 3. sata controller 2 is only visible when d31:f2 cc.scc=01h. bus 0:device 29:function 1 usb fs/ls uhci controller #2 bus 0:device 29:function 2 usb fs/ls uhci controller #3 bus 0:device 29:function 3 usb fs/ls uhci controller #6 2 bus 0:device 29:function 7 usb hs ehci controller #1 bus 0:device 26:function 0 usb fs/ls uhci controller #4 bus 0:device 26:function 1 usb fs/ls uhci controller #5 bus 0:device 26:function 2 usb fs/ls uhci controller #6 2 bus 0:device 26:fucntion 7 usb hs ehci controller #2 bus 0:device 28:function 0 pci express* port 1 bus 0:device 28:function 1 pci express port 2 bus 0:device 28:function 2 pci express port 3 bus 0:device 28:function 3 pci express port 4 bus 0:device 28:function 4 pci express port 5 bus 0:device 28:function 5 pci express port 6 bus 0:device 27:function 0 intel ? high definition audio controller bus 0:device 25:function 0 gigabit ethernet controller table 1-2. pci devices and functions (sheet 2 of 2) bus:device:function function description http://www..net/ datasheet pdf - http://www..net/ datasheetcdi / ibl #: 373635 39 introduction 1.2.1 capability overview the following sub-sections provide an overview of the ich10 capabilities. direct media interface (dmi) direct media interface (dmi) is the chip-to-chip connection between the memory controller hub / graphics memory controller hub ((g)mch) and i/o controller hub 10 (ich10). this high-speed interface integr ates advanced priority-based servicing allowing for concurrent traffic and true isochronous transfer capabilities. base functionality is completely software-tra nsparent, permitting current and legacy software to operate normally. pci express* interface the ich10 provides up to 6 pci ex press root ports, supporting the pci express base specification, revision 1.1. each root port supports 2.5 gb/s bandwidth in each direction (5 gb/s concurrent). pci express root ports 1?4 can be statically configured as four x1 ports or ganged together to form one x4 port. ports 5 and 6 can only be used as two x1 ports. note: the integrated gigabit ethernet controllers data lines for 1000 mb/s speed are multiplexed with pci express* root port 6 and therefore unavailable if a gigabit ethernet phy is connected. the use of a 10/100 mb/s phy does not consume pci express root port 6 and therefore the port is available to be utilized as a x1 port. serial ata (sata) controller the ich10 has two integrated sata host controllers that support independent dma operation on up to six ports and supports data transfer rates of up to 3.0 gb/s (300 mb/s). the sata controller contains two modes of operation ? a legacy mode using i/o space, and an ahci mode using me mory space. software that uses legacy mode will not have ahci capabilities. the ich10 supports the serial ata specification , revision 1.0a. the ich10 also supports several optional sections of the serial ata ii: extensions to serial ata 1.0 specification , revision 1.0 (ahci support is required for some elements). ahci the ich10 provides hardware support for ad vanced host controller interface (ahci), a new programming interface for sata host controllers. platforms supporting ahci may take advantage of performance features such as no master/slave designation for sata devices?each device is treated as a master?and hardware-assisted native command queuing. ahci also provides usability enhanc ements such as hot-plug. ahci requires appropriate software support (e.g., an ahci driver) and for some features, hardware support in the sata device or additional platform hardware. see section 1.3 for details on component feature availability. intel ? matrix storage technology the ich10 provides support for intel? matrix storage technology, providing both ahci (see above for details on ahci) and integrated raid functionality. the industry-leading raid capability provides high-performance raid 0, 1, 5, and 10 functionality on up to 6 sata ports of ich10. matrix raid support is provided to allow multiple raid levels to be combined on a single set of hard drives, such as raid 0 and raid 1 on two disks. other raid features include hot spare su pport, smart alerting, and raid 0 auto replace. software components include an option rom for pre-boot configuration and http://www..net/ datasheet pdf - http://www..net/ introduction 40 datasheetcdi / ibl #: 373635 boot functionality, a microsoft windows* co mpatible driver, and a user interface for configuration and management of th e raid capability of ich10. see section 1.3 for details on component feature availability. pci interface the ich10 pci interface provides a 33 mhz, revision 2.3 implementation. the ich10 integrates a pci arbiter that supports up to four external pci bus masters in addition to the internal ich10 requests. this allows for combinations of up to four pci down devices and pci slots. low pin count (lpc) interface the ich10 implements an lpc interface as described in the lpc 1.1 specification . the low pin count (lpc) bridge function of the ich10 resides in pci device 31:function 0. in addition to the lpc bridge interface function, d31:f0 contains other functional units including dma, interrupt controllers, time rs, power management, system management, gpio, and rtc. serial peripheral interface (spi) the ich10 implements an spi interface as an alternative interface for the bios flash device. an spi flash device can be used as a replacement for the fwh, and is required to support gigabit ethernet, intel ? active management technology, and integrated intel ? quiet system technology. the ich10 supports up to two spi flash devices with speed up to 33 mhz using two chip select pins. compatibility modules (dma contro ller, timer/counters, interrupt controller) the dma controller incorporates the logic of two 82c37 dma controllers, with seven independently programmable channels. channels 0?3 are hardwired to 8-bit, count-by- byte transfers, and channels 5?7 are hard wired to 16-bit, count-by-word transfers. any two of the seven dma channels can be programmed to support fast type-f transfers. channel 4 is reserved as a generic bus master request. the ich10 supports lpc dma, which is similar to isa dma, through the ich10?s dma controller. lpc dma is handled through the use of the ldrq# lines from peripherals and special encoding on lad[3:0] from the host. single, demand, verify, and increment modes are suppor ted on the lpc interface. the timer/counter block contains three counters that are equivalent in function to those found in one 82c54 programmable interval timer. these three counters are combined to provide the system timer function, and speaker tone. the 14.31818 mhz oscillator input provides the clock source for these three counters. the ich10 provides an isa-compatible programmable interrupt controller (pic) that incorporates the functionality of two, 82c59 interrupt controllers. the two interrupt controllers are cascaded so that 14 external and two internal interrupts are possible. in addition, the ich10 supports a serial interrupt scheme. all of the registers in these modules can be read and restored. this is required to save and restore system state after power has be en removed and restored to the platform. advanced programmable interrupt controller (apic) in addition to the standard isa compatible programmable interrupt controller (pic) described in the previous section, the ich 10 incorporates the advanced programmable interrupt controller (apic). http://www..net/ datasheet pdf - http://www..net/ datasheetcdi / ibl #: 373635 41 introduction universal serial bus (usb) controllers the ich10 contains up to two enhanced host controller interface (ehci) host controllers that support usb high-speed signaling. high-speed usb 2.0 allows data transfers up to 480 mb/s which is 40 times faster than full-speed usb. the ich10 also contains up to six universal host controller interface (uhci) controllers that support usb full-speed and low-speed signaling. the ich10 supports up to twelve usb 2.0 po rts. all twelve ports are high-speed, full- speed, and low-speed capable. ich10?s port -routing logic determines whether a usb port is controlled by one of the uhci or ehci controllers. see section 5.18 and section 5.19 for details. gigabit ethernet controller the gigabit ethernet controller provides a system interface via a pci function. the controller provides a full memory-mapped or io mapped interface along with a 64 bit address master support for systems using more than 4 gb of physical memory and dma (direct memory addressing) mechanisms for high performance data transfers. its bus master capabilities enable the component to process high-level commands and perform multiple operations; this lowe rs processor utilization by off-loading communication tasks from the processor. two large configurable transmit and receive fifos (up to 20 kb each) help prevent data underruns and overruns while waiting for bus accesses. this enables the integrated lan controller to transmit data with minimum interframe spacing (ifs). the lan controller can operate at multiple speeds (10/100/1000 mb/s) and in either full duplex or half duplex mode. in full dupl ex mode the lan contro ller adheres with the ieee 802.3x flow control specification. half duplex performance is enhanced by a proprietary collision reduction mechanism. see section 5.3 for details. rtc the ich10 contains a motorola mc146818a-compatible real-time clock with 256 bytes of battery-backed ram. the real-time clock performs two key functions: keeping track of the time of day and storing system data, even when the system is powered down. the rtc operates on a 32.768 khz crystal and a 3 v battery. the rtc also supports two lockable memory ranges. by setting bits in the configuration space, two 8-byte ranges can be locked to read and write accesses. this prevents unauthorized reading of passwords or other system security information. the rtc also supports a date alarm that allows for scheduling a wake up event up to 30 days in advance, rather than just 24 hours in advance. gpio various general purpose inputs and outputs are provided for custom system design. the number of inputs and outputs varies depending on ich10 configuration. enhanced power management the ich10?s power management functions include enhanced clock control and various low-power (suspend) states (e.g., suspend- to-ram and suspend-to-disk). a hardware- based thermal management circuit permits software-independent entrance to low- power states. the ich10 contains full support for the advanced configuration and power interface (acpi) specification, revision 3.0a. http://www..net/ datasheet pdf - http://www..net/ introduction 42 datasheetcdi / ibl #: 373635 intel ? active management technology (intel ? amt) (not available on all ich10 components) intel ? active management technology is the next generation of client manageability via the wired network. intel amt is a set of ad vanced manageability features developed as a direct result of it customer feedback ga ined through intel market research. with the new implementation of system defense in ich10, the advanced manageability feature set of intel amt is further enhanced. see section 1.3 for details on component feature availability. manageability in addition to intel amt, ich10 integrates several functions designed to manage the system and lower the total cost of owne rship (tco) of the system. these system management functions are designed to report errors, diagnose the system, and recover from system lockups without the aid of an external microcontroller. ? tco timer. the ich10?s integrated programmab le tco timer is used to detect system locks. the first expiration of the timer generates an smi# that the system can use to recover from a software lock. the second expiration of the timer causes a system reset to recover from a hardware lock. ? processor present indicator. the ich10 looks for the processor to fetch the first instruction after reset. if the processor does not fetch the first instruction, the ich10 will reboot the system. ? ecc error reporting. when detecting an ecc error, the host controller has the ability to send one of several messages to the ich10. the host controller can instruct the ich10 to generate either an smi#, nmi, serr#, or tco interrupt. ? function disable. the ich10 provides the ability to disable the following integrated functions: lan, usb, lpc, intel hd audio, sata, pci express or smbus. once disabled, these functions no longer decode i/o, memory, or pci configuration space. also, no interrupts or power management events are generated from the disabled functions. ? intruder detect. the ich10 provides an input signal (intruder#) that can be attached to a switch that is activated by the system case being opened. the ich10 can be programmed to generate an smi# or tco interrupt due to an active intruder# signal. system management bus (smbus 2.0) the ich10 contains an smbus host interface that allows the processor to communicate with smbus slaves. this interface is compatible with most i 2 c devices. special i 2 c commands are implemented. the ich10?s smbus host controller provides a mechanism for the processor to initiate communications with smbus peripherals (slaves). also, the ich10 supports slave functionality, including the host notify pr otocol. hence, the host controller supports eight command protocols of the smbus interface (see system management bus (smbus) specification, version 2.0): quick command, se nd byte, receive byte, write byte/word, read byte/word, process ca ll, block read/write, and host notify. ich10?s smbus also implements hardware-based packet error checking for data robustness and the address resolution protoc ol (arp) to dynamically provide address to all smbus devices. http://www..net/ datasheet pdf - http://www..net/ datasheetcdi / ibl #: 373635 43 introduction intel ? high definition audio controller the intel ? high definition audio specification defines a digital interface that can be used to attach different types of codecs, such as audio and modem codecs. the ich10 intel ? hd audio controller supports up to 4 codecs. the link can operate at either 3.3 v or 1.5 v. with the support of multi-channel audio stream, 32-bit sample depth, and sample rate up to 192 khz, the intel ? hd audio controller provides audio quality that can deliver ce levels of audio experience. on the input si de, the ich10 adds support for an array of microphones. intel ? quiet system technology (intel ? qst) the ich10 integrates four fan speed sensors (four tach signals) and 3 fan speed controllers (three pulse width modulator signals), which enables monitoring and controlling up to four fans on the system. with the new implementation of the single- wire simple serial transport (sst) 1.0 bus and platform environmental control interface (peci), the ich10 provides an ea sy way to connect to sst-based thermal sensors and access the processor thermal data. in addition, coupled with the new sophisticated fan speed control algorithms, intel ? qst provides effective thermal and acoustic management for the platform. note: intel ? quiet system technology functionality requires a correctly configured system, including an appropriate (g)mch with inte l me, intel me firmware, and system bios support. intel ? trusted platform modu le (corporate only) the intel trusted platform module (intel ? tpm) implementation consists of firmware, intel ? management engine resources and dedicated hardware within the ich and the (g)mch. the intel tpm supports all requirements of the tpm specification version 1.2, revision 103, as published by the truste d computing group. the intel tpm behaves like a discrete tpm device, and can support third party applications, as well as microsoft* specific functionality in the windows vista* os. note: intel tpm functionality requires a correctly configured system, including an appropriate (g)mch with intel management engine firmware, ich10 and spi flash. jtag boundary-scan (corporate only) ich10 adds the industry standard jtag in terface and enables boundary-scan in place of the xor chains used in previous generations of the ich. boundary-scan can be used to ensure device connectivity during the board manufacturing process. the jtag interface allows system manufacturers to impr ove efficiency by usin g industry available tools to test the ich on an assembled boar d. since jtag is a serial interface, it eliminates the need to create probe points for every pin in an xor chain. this eases pin breakout and trace routing and simplifies the interface between the system and a bed- of-nails tester. note: contact your local intel field sales representative for additional information about jtag usage on ich10. http://www..net/ datasheet pdf - http://www..net/ introduction 44 datasheetcdi / ibl #: 373635 1.3 intel ? ich10 family high-level component differences notes: 1. contact your local intel field sales represen tative for currently available ich10 components. 2. table above shows feature difference between ich10 components. if a feature is not listed in the table it is considered a base feature th at is included in all components. 3. ich10 consumer base provides hardware suppo rt for ahci functionality when enabled by appropriate system configuration and software driver. 4. wake on voip support provided by intel ? remote wake technology (intel ? rwt) support. 5. all components support 6 sata, 6 pcie*, and 14 usb ports. table 1-3. intel ? ich10 components feature consumer corporate ich10 ich10r ich10d ich10do component name ich10 consumer base ich10 raid ich10 corporate base ich10 digital office intel ? turbo memory support no yes no no intel ? matrix storage technology ahci no 3 yes yes yes raid 0/1/5/10 support no yes no yes intel ? active management technology release 5.0 basic no no yes no professional no no no yes intel ? trusted platform module (intel ? tpm) no no yes yes wake on voip yes 4 yes 4 no no intel ? viiv? processor technology support yes yes no no intel ? remote wake technology (intel ? rwt) support yes yes no no jtag boundary scan no no yes yes http://www..net/ datasheet pdf - http://www..net/ datasheet 45 signal description 2 signal description this chapter provides a detailed description of each signal. the signals are arranged in functional groups according to their associated interface. the ?#? symbol at the end of the signal na me indicates that the active, or asserted state occurs when the signal is at a low voltage level. when ?#? is not present, the signal is asserted when at the high voltage level. the following notations are used to describe the signal type: i input pin o output pin od o open-drain output pin. i/od bi-directional input/open-drain output pin. i/o bi-directional input / output pin. the ?type? for each signal is indicative of the functional operating mode of the signal. unless otherwise noted in section 3.2 or section 3.3 , a signal is considered to be in the functional operating mode after rtcrst# de asserts for signals in the rtc well, after rsmrst# deasserts for signals in the suspen d well, after pwrok asserts for signals in the core well, and after lan_rst# de asserts for signals in the lan well. http://www..net/ datasheet pdf - http://www..net/ signal description 46 datasheet notes: 1. symbol indicates a particular use of a pin is cunsumer only. 2. ? symbol indicates a particular use of a pin is corporate only. figure 2-1. intel ? ich10 interface signals block diagram thrm# thrmtrip# sys_reset# rsmrst# mch_sync# slp_s3# slp_s4# slp_s5#/gpio63 ? slp_m# s4_state#/gpio26 pwrok clpwrok pwrbtn# ri# wake# sus_stat#/lpcpd/gpio61 ? susclk/gpio62 ? lan_rst# vrmpwrgd pltrst# ck_pwrgd bmbusy#/gpio0 stp_pci#/gpio15 stp_cpu#/gpio25 ? drampwrok ? /gpio8 dprstp# dprslpvr / gpio16 ad[31:0] c/be[3:0]# devsel# frame# irdy# trdy# stop# par perr# req0# req1#/gpio50 req2#/gpio52 req3#/gpio54 gnt0# gnt1#/gpio51 gnt2#/gpio53 gnt3#/gpio55 serr# pme# pciclk pcirst# plock# pci interface lan_rstsync glan_clk glan_txp/petp6; glan_txn/petn6 glan_rxp/perp6; glan_rxn/pern6 glan_compo glan_compi gigabit lan connect interface power mgnt. interrupt interface a20m# ferr# ignne# init# init3_3v# intr nmi smi# stpclk# rcin# a20gate cpupwrgd dpslp# processor interface usb serirq pirq[d:a]# pirq[h:e]#/gpio[5:2] usb[11:0]p; usb[11:0]n oc0#/gpio59; oc1#/gpio40 oc2#/gpio41; oc3#/gpio42 oc4#/gpio43; oc5#/gpio29 oc6#/gpio30; oc7#/gpio31 oc8#/gpio44; oc9#/gpio45 oc10#/gpio46; oc11#/gpio47 usbrbias usbrbias# rtcx1 rtcx2 clk14 clk48 sata_clkp, sata_clkn dmi_clkp, dmi_clkn rtc clocks misc. signals intvrmen spkr srtcrst#; rtcrst# tp[5:4] tp7 tp6 gpio72 ? / tp0 lan100_slp general purpose i/o gpio[72,49,34,33,32,28, 27,20,18,16,13,12,0] pwm[2:0] tach0/gpio17; tach1/gpio1 tach2/gpio6; tach3/gpio7 sst peci intruder#; smlink[1:0] linkalert#/gpio60 gpio24/mem_led; gpio10/cpu_missing/jtagtms ? gpio14/jtagtdi ? gpio57/tpm_pp/jtagtck ? spi_cs1#/gpio58 ; wol_en/gpio9 dmi[3:0]txp, dmi[3:0]txn dmi[3:0]rxp, dmi[3:0]rxn dmi_zcomp dmi_ircomp direct media interface lpc interface smbus interface hda_rst# hda_sync hda_bit_clk hda_sdout hda_sdin[3:0] intel ? high definition audio firmware hub system mgnt. fwh[3:0]/lad[3:0] fwh4/lframe# lad[3:0]/fwh[3:0] lframe#/fwh4 ldrq0# ldrq1#/gpio23 smbdata smbclk gpio11/smbalert#/jtagtdo ? glan_clk lan_rxd[2:0] lan_txd[2:0] lan_rstsync lan connect interface sata[5:0]txp, sata[5:0]txn sata[5:0]rxp, sata[5:0]rxn satarbias satarbias# sataled# sataclkreq#/gpio35 sata0gp/gpio21 sata1gp/gpio19 sata2gp/gpio36 sata3gp/gpio37 sata4gp sata5gp sclock/gpio22 sload/gpio38 sdataout0/gpio39 sdataout1/gpio48 serial ata interface pci express* interface petp[5:1], petn[5:1] perp[5:1], pern[5:1] glan_txp/petp6; glan_txn/petn6 glan_rxp/perp6; glan_rxn/pern6 spi spi_cs0# spi_cs1#/gpio58 spi_miso spi_mosi spi_clk jtag (corporate only) cl_clk0 ; cl_data0 cl_vref0 cl_rst0# controller link fan speed control gpio57/tpm_pp/jtagtck ? gpio10/cpu_missing/jtagtms ? gpio14/jtagtdi ? gpio11/smbalert#/jtagtdo ? gpio60/linkalert#/jtagrst# ? http://www..net/ datasheet pdf - http://www..net/ datasheet 47 signal description 2.1 direct media interface (dmi) to host controller table 2-1. direct me dia interface signals name type description dmi0txp, dmi0txn o direct media interface diff erential transmit pair 0 dmi0rxp, dmi0rxn i direct media interface diff erential receive pair 0 dmi1txp, dmi1txn o direct media interface diff erential transmit pair 1 dmi1rxp, dmi1rxn i direct media interface diff erential receive pair 1 dmi2txp, dmi2txn o direct media interface diff erential transmit pair 2 dmi2rxp, dmi2rxn i direct media interface diff erential receive pair 2 dmi3txp, dmi3txn o direct media interface diff erential transmit pair 3 dmi3rxp, dmi3rxn i direct media interface diff erential receive pair 3 dmi_zcomp i impedance compensation input: determines dmi input impedance. dmi_ircomp o impedance/current compensation output: determines dmi output impedance and bias current. http://www..net/ datasheet pdf - http://www..net/ signal description 48 datasheet 2.2 pci express* interface 2.3 lan connect interface table 2-2. pci express* signals name type description petp1, petn1 o pci express* differenti al transmit pair 1 perp1, pern1 i pci express differential receive pair 1 petp2, petn2 o pci express differential transmit pair 2 perp2, pern2 i pci express differential receive pair 2 petp3, petn3 o pci express differential transmit pair 3 perp3, pern3 i pci express differential receive pair 3 petp4, petn4 o pci express differential transmit pair 4 perp4, pern4 i pci express differential receive pair 4 petp5, petn5 o pci express differential transmit pair 5 perp5, pern5 i pci express differential receive pair 5 petp6 / glan_txp, petn6 / glan_txn o pci express differential transmit pair 6: the differential pair will function as the gigabit lan connect interface transmit pair when the integrated gigabit lan controller is enabled. perp6 / glan_rxp, pern6 / glan_rxn i pci express differential receive pair 6: the differential pair will function as the gigabit lan connect interface receive pair when the integrated gigabit lan controller is enabled. table 2-3. lan connect interface signals name type description glan_clk i gigabit lan input clock: clock driven by the platform lan connect device. the frequency will va ry depending on link speed. note: the clock is shared between the lan connect interface and the gigabit lan connect interface. lan_rxd[2:0] i received data: the platform lan connect device uses these signals to transfer data and control in formation to the integrated lan controller. these signals have integrated weak pull-up resistors. http://www..net/ datasheet pdf - http://www..net/ datasheet 49 signal description 2.4 gigabit lan connect interface lan_txd[2:0] o transmit data : the integrated lan controller uses these signals to transfer data and control informat ion to the platfo rm lan connect component. lan_rstsync o lan reset/sync: this is the reset/sync signal from the lan connect interface to the physic al device. the platform lan connect device?s reset and sync signals are mu ltiplexed onto this pin. note: the signal is shared between lan connect interface and gigabit lan conn ect interface. lan_phy_pw r_ctrl / gpio12 o lan phy power control: this signal may optionally be connected to a switch to turn 3.3 v phy power off when lan is disabled for additional power savings. this capa bility is configured in the nvm. when using an 82567 phy solution , the lan_phy_pwr_ctrl signal should be connected to the phy?s lan_disable_n pin for a hardware based lan disable mechanism. signal can instead be used as gpio12. table 2-4. gigabit lan co nnect interface signals name type description glan_clk i gigabit lan input clock: clock driven by the platform lan connect device. th e frequency will vary de pending on link speed. note: the clock is shared betwee n the lan connect interface and the gigabit lan connect interface. glan_txp /petp6; glan_txn /petn6 o gigabit lan differential transmit pair. can be instead used as pci express port 6 di fferential transmit pair. glan_rxp /perp6; glan_rxn /pern6 i gigabit lan differential receive pair . can be instead used as pci express port 6 differential receive pair. glan_compo o impedance compensation output pad: determines gigabit lan connect interface output impedance and bias current. glan_compi i impedance compensation input pad: determines gigabit lan connect interface input impedance. lan_rstsync o lan reset/sync: this is the reset/sync signal from the gigabit lan interface to the physical de vice. the platform lan connect device?s reset and sync signals are multiplexed onto this pin. note: the signal is shared between lan connect interface and gigabit lan connect interface. table 2-3. lan connect interface signals name type description http://www..net/ datasheet pdf - http://www..net/ signal description 50 datasheet 2.5 firmware hub interface 2.6 pci interface table 2-5. firmware hub interface signals name type description fwh[3:0] / lad[3:0] i/o firmware hub signals. these signals are mult iplexed with the lpc address signals. fwh4 / lframe# o firmware hub signals. this signal is multiplexed with the lpc lframe# signal. init3_3v# o initialization 3.3 v: this is the identical 3.3 v copy of init# intended for firmware hub. table 2-6. pci interface signals (sheet 1 of 3) name type description ad[31:0] i/o pci address/data : ad[31:0] is a multip lexed address and data bus. during the first clock of a transaction, ad[31:0] contain a physical address (32 bi ts). during subseque nt clocks, ad[31:0] contain data. the intel ich10will drive all 0s on ad[31:0] during the address phase of all pci special cycles. c/be[3:0]# i/o bus command and byte enables : the command and byte enable signals are multiplexed on the sa me pci pins. duri ng the address phase of a transaction, c/be[3:0]# define the bus command. during the data phase c/be[3:0 ]# define the byte enables. all command encodings not shown are reserved. the ich10 does not decode reserved values, and th erefore will not respond if a pci master generates a cycle using one of the reserved values. devsel# i/o device select : the ich10 asserts devsel# to claim a pci transaction. as an output, the ich10 asserts devsel# when a pci master peripheral attempts an acce ss to an internal ich10 address or an address destined for dmi (main memory or graphics). as an input, devsel# indicates the re sponse to an ich10-initiated transaction on the pci bus. devsel# is tri-stated from the leading edge of pltrst#. devsel# remain s tri-stated by the ich10 until driven by a target device. c/be[3:0]# command type 0000b interrupt acknowledge 0001b special cycle 0010b i/o read 0011b i/o write 0110b memory read 0111b memory write 1010b configuration read 1011b configuration write 1100b memory read multiple 1110b memory read line 1111b memory write and invalidate http://www..net/ datasheet pdf - http://www..net/ datasheet 51 signal description frame# i/o cycle frame: the current initiator drives frame# to indicate the beginning and duration of a pci transaction. while the initiator asserts frame#, data transfers continue. when the initiator negates frame#, the transaction is in the final data phase. frame# is an input to the ich10 when the ich10 is the target, and frame# is an output from the ich10 when the ich10 is the initiator. frame# remains tri-stated by the ich10 until driven by an initiator. irdy# i/o initiator ready : irdy# indicates the ich10's ability, as an initiator, to complete the current data phase of the transaction. it is used in conjunction with trdy#. a data phase is completed on any clock both irdy# and trdy# are sa mpled asserted. during a write, irdy# indicates the ich10 has valid data present on ad[31:0]. during a read, it indicates the ic h10 is prepared to latch data. irdy# is an input to the ich10 when the ich10 is the target and an output from the ich10 when the ich10 is an initiator. irdy# remains tri-stated by the ich10 until driven by an initiator. trdy# i/o target ready : trdy# indicates the ich10's ability as a target to complete the current data phase of the transaction. trdy# is used in conjunction with irdy#. a data phase is completed when both trdy# and irdy# are sampled a sserted. during a read, trdy# indicates that the ich10, as a ta rget, has placed valid data on ad[31:0]. during a write, trdy# indicates the ich10, as a target is prepared to latch data. trdy# is an input to the ich10 when the ich10 is the initiator and an output from the ich10 when the ich10 is a target. trdy# is tri- stated from the leading edge of pltrst#. trdy# remains tri-stated by the ich10 until driven by a target. stop# i/o stop : stop# indicates that the ich10, as a target, is requesting the initiator to stop the current transaction. stop# causes the ich10, as an initiator, to stop th e current transactio n. stop# is an output when the ich10 is a target and an input when the ich10 is an initiator. par i/o calculated/checked parity: par uses ?even? parity calculated on 36 bits, ad[31:0] plus c/be[3:0]# . ?even? parity means that the ich10 counts the number of ones within the 36 bits plus par and the sum is always even. the ich10 always calculates par on 36 bits regardless of the valid byte enab les. the ich10 generates par for address and data phases and only ensures par to be valid one pci clock after the corresponding addr ess or data phase. the ich10 drives and tri-states par identically to the ad[31:0] lines except that the ich10 delays par by ex actly one pci clock. par is an output during the address phase (delayed one clock) for all ich10 initiated transactions. par is an output during the data phase (delayed one clock) when the ich10 is the initiator of a pci write transaction, and when it is the ta rget of a read transaction. ich10 checks parity when it is the target of a pci write transaction. if a parity error is detected, the ich10 will set the appropriate internal status bits, and has the option to generate an nmi# or smi#. perr# i/o parity error : an external pci device drives perr# when it receives data that has a parity error. the ich10 drives perr# when it detects a parity error. the ich10 can either generate an nmi# or smi# upon detecting a parity erro r (either detected internally or reported via the perr# signal). table 2-6. pci interface signals (sheet 2 of 3) name type description http://www..net/ datasheet pdf - http://www..net/ signal description 52 datasheet 2.7 serial ata interface bh req0# req1#/ gpio50 req2#/ gpio52 req3#/ gpio54 i pci requests : the ich10 supports up to 4 masters on the pci bus. req[3:1]# pins can instead be used as gpio. gnt0# gnt1#/ gpio51 gnt2# / gpio53 gnt3# /gpio55 o pci grants : the ich10 supports up to 4 masters on the pci bus. gnt[3:1]# pins can instead be used as gpio. pull-up resistors are not required on these signals. if pull-ups are used, they should be tied to the vcc3_3 power rail. note: gnt[3:0]# are sampled as a functional strap. see section 2.25.1 for details. pciclk i pci clock : this is a 33 mhz clock. pciclk provides timing for all transactions on the pci bus. pcirst# o pci reset: this is the secondary pci bus reset signal. it is a logical or of the primary interface pltrst# signal and the state of the secondary bus reset bit of the bridge control register (d30:f0:3eh, bit 6). plock# i/o pci lock : this signal indicates an ex clusive bus operation and may require multiple transactions to complete. ich10 asserts plock# when it performs non-exclusive transactions on the pci bus. plock# is ignored when pci masters are granted the bus. serr# i/od system error : serr# can be pulsed active by any pci device that detects a system error condition. upon sampling serr# active, the ich10 has the ability to generate an nmi, smi#, or interrupt. pme# i/od pci power management event : pci peripherals drive pme# to wake the system from low-power states s1?s5. pme# assertion can also be enabled to generate an sci from the s0 state. in some cases the ich10 may drive pme# active due to an internal wake event. the ich10 will not drive pme# high, but it will be pulled up to vccsus3_3 by an inte rnal pull-u p resistor. table 2-7. serial ata interf ace signals (sheet 1 of 3) name type description sata0txp sata0txn o serial ata 0 differenti al transmit pairs: these are outbound high-speed differential signals to port 0. in compatible mode, sata port 0 is the primary master of sata controller 1. sata0rxp sata0rxn i serial ata 0 differential receive pair: these are inbound high- speed differential si gnals from port 0. in compatible mode, sata port 0 is the primary master of sata controller 1. sata1txp sata1txn o serial ata 1 differential transmit pair: these are outbound high-speed differentia l signals to port 1. in compatible mode, sata port 1 is the secondary master of sata controller 1. table 2-6. pci interface signals (sheet 3 of 3) name type description http://www..net/ datasheet pdf - http://www..net/ datasheet 53 signal description sata1rxp sata1rxn i serial ata 1 differential receive pair: these are inbound high- speed differential si gnals from port 1. in compatible mode, sata port 1 is the secondary master of sata controller 1 sata2txp sata2txn o serial ata 2 differential transmit pair: these are outbound high-speed differentia l signals to port 2. in compatible mode, sata port 2 is the primary slave of sata controller 1. sata2rxp sata2rxn i serial ata 2 differential receive pair: these are inbound high- speed differential si gnals from port 2. in compatible mode, sata port 2 is the primary slave of sata controller 1 sata3txp sata3txn o serial ata 3 differential transmit pair: these are outbound high-speed differentia l signals to port 3. in compatible mode, sata port 3 is the secondary slave of sata controller 1 sata3rxp sata3rxn i serial ata 3 differential receive pair: these are inbound high- speed differential si gnals from port 3. in compatible mode, sata port 3 is the secondary slave of sata controller 1 sata4txp sata4txn o serial ata 4 differential transmit pair: these are outbound high-speed differentia l signals to port 4. in compatible mode, sata port 4 is the primary master of sata controller 2 sata4rxp sata4rxn i serial ata 4 differential receive pair: these are inbound high- speed differential si gnals from port 4. in compatible mode, sata port 4 is the primary master of sata controller 2 sata5txp sata5txn o serial ata 5 differential transmit pair: these are outbound high-speed differentia l signals to port 5. in compatible mode, sata port 5 is the secondary master of sata controller 2 sata5rxp sata5rxn i serial ata 5 differential receive pair: these are inbound high- speed differential si gnals from port 5. in compatible mode, sata port 5 is the secondary master of sata controller 2 satarbias o serial ata resistor bias: this is an analog connection point for an external resistor to ground. satarbias# i serial ata resistor bias complement: this is an analog connection point for an exte rnal resistor to ground. sata0gp / gpio21 i serial ata 0 general purpose: this is an input pin which can be configured as an interlock switch corresponding to sata port 0. when used as an interlock switch status indication, this signal should be drive to ?0? to indicate that the switch is closed and to ?1? to indicate that the switch is open. if interlock switches are not requir ed, this pin can be configured as gpio21. table 2-7. serial ata interf ace signals (sheet 2 of 3) name type description http://www..net/ datasheet pdf - http://www..net/ signal description 54 datasheet sata1gp / gpio19 i serial ata 1 general purpose: same function as sata0gp, except for sata port 1. if interlock switches ar e not required, this pin can be configured as gpio19. sata2gp / gpio36 i serial ata 2 general purpose: same function as sata0gp, except for sata port 2. if interlock switches ar e not required, this pin can be configured as gpio36. note: this signal can also be used as gpio36. sata3gp / gpio37 i serial ata 3 general purpose: same function as sata0gp, except for sata port 3. if interlock switches ar e not required, this pin can be configured as gpio37. note: this signal can also be used as gpio37. sata4gp i serial ata 4 general purpose: same function as sata0gp, except for sata port 4. sata5gp i serial ata 5 general purpose: same function as sata0gp, except for sata port 5. sataled# od o serial ata led: this signal is an open -drain output pin driven during sata command activity. it is to be connected to external circuitry that can provide the current to drive a platform led. when active, the led is on. when tri-stated, the led is off. an external pull-up resistor to vcc3_3 is required. note: this signal is sampled as a functional strap. see section 2.25.1 for details. sataclkreq# /gpio35 od o serial ata clock request: this signal is an open-drain output pin when configured as sataclkreq#. it is used to connect to the system clock chip. when active, re quest for sata clock running is asserted. when tri-stated, it tells the clock chip that sata clock can be stopped. an external pu ll-up resistor is required. sclock / gpio22 od o sgpio reference clock: the sata controller uses rising edges of this clock to transmit serial data , and the target uses the falling edge of this clock to latch data. if sgpio interface is not used, this signal can be used as a gpio. sload /gpio38 od o sgpio load: the controller drives a ?1? at the rising edge of sclock to indicate either the star t or end of a bit stream. a 4-bit vendor specific pattern will be transmitted right after the signal assertion. if sgpio interface is not used, this signal can be used as a gpio. sdataout0 / gpio39 sdataout1 / gpio48 od o sgpio dataout: driven by the controller to indicate the drive status in the following sequence: drive 0, 1, 2, 3, 4, 5, 0, 1, 2... if sgpio interface is not used, th e signals can be used as gpio. table 2-7. serial ata interf ace signals (sheet 3 of 3) name type description http://www..net/ datasheet pdf - http://www..net/ datasheet 55 signal description 2.8 lpc interface 2.9 interrupt interface table 2-8. lpc interface signals name typ e description lad[3:0] / fwh[3:0] i/o lpc multiplexed command, address, data: for lad[3:0], internal pull- ups are provided. lframe# / fwh4 o lpc frame: lframe# indicates the start of an lpc cycle, or an abort. ldrq0#, ldrq1# / gpio23 i lpc serial dma/master request inputs: ldrq[1:0]# are used to request dma or bus master access. these signals are typically connected to an external super i/o device. an inte rnal pull-up resistor is provided on these signals. ldrq1# may optionally be used as gpio. table 2-9. interrupt signals name type description serirq i/od serial interrupt request: this pin implements the serial interrupt protocol. pirq[d:a]# i/od pci interrupt requests: in non-apic mode the pirqx# signals can be routed to interrupts 3, 4, 5, 6, 7, 9, 10, 11, 12, 14 or 15 as described in section 5.8.6 . each pirqx# line has a separate route control register. in apic mode, these signals are connected to the internal i/o apic in the following fashion: pirqa# is connected to irq16, pirqb# to irq17, pirqc# to irq18, and pi rqd# to irq19. this frees the legacy interrupts. pirq[h:e]# / gpio[5:2] i/od pci interrupt requests: in non-apic mode the pirqx# signals can be routed to interrupts 3, 4, 5, 6, 7, 9, 10, 11, 12, 14 or 15 as described in section 5.8.6 . each pirqx# line has a separate route control register. in apic mode, these signals are connected to the internal i/o apic in the following fashion: pirqe# is connected to irq20, pirqf# to irq21, pirqg# to irq22, and pirqh# to irq23. this frees the legacy interrupts. if not needed fo r interrupts, thes e signals can be used as gpio. http://www..net/ datasheet pdf - http://www..net/ signal description 56 datasheet 2.10 usb interface table 2-10. usb interface signals name typ e description usbp0p, usbp0n, usbp1p, usbp1n i/o universal serial bus port [1:0] differential : these differential pairs are used to transmit data/a ddress/command sign als for ports 0 and 1. these ports can be routed to uhci controller #1 or the ehci controller #1. note: no external resistors are required on these signals. the intel ich10 integrates 15 k pull-downs and provides an output driver impedance of 45 which requires no external series resistor. usbp2p, usbp2n, usbp3p, usbp3n i/o universal serial bus port [3:2] differential : these differential pairs are used to transmit data/a ddress/command signals for ports 2 and 3. these ports can be routed to uhci controller #2 or the ehci controller #1. note: no external resistors are requir ed on these signals. the ich10 integrates 15 k pull-downs and provides an output driver impedance of 45 which requires no exte rnal series resistor. usbp4p, usbp4n, usbp5p, usbp5n i/o universal serial bus port [5:4] differential : these differential pairs are used to transmit data/a ddress/command sign als for ports 4 and 5. these ports can be routed to uhci controller #3 or the ehci controller #1. note: no external resistors are requir ed on these signals. the ich10 integrates 15 k pull-downs and provides an output driver impedance of 45 which requires no exte rnal series resistor. usbp6p, usbp6n, usbp7p, usbp7n i/o universal serial bus port [7:6] differential : these differential pairs are used to transmit data/a ddress/command sign als for ports 6 and 7. these ports can be routed to uhci controller #4 or the ehci controller #2. note: no external resistors are requir ed on these signals. the ich10 integrates 15 k pull-downs and provides an output driver impedance of 45 which requires no exte rnal series resistor. usbp8p, usbp8n, usbp9p, usbp9n i/o universal serial bus port [9:8] differential : these differential pairs are used to transmit data/a ddress/command sign als for ports 8 and 9. these ports can be routed to uhci controller #5 or the ehci controller #2. note: no external resistors are requir ed on these signals. the ich10 integrates 15 k pull-downs and provides an output driver impedance of 45 which requires no exte rnal series resistor. http://www..net/ datasheet pdf - http://www..net/ datasheet 57 signal description usbp10p, usbp10n, usbp11p, usbp11n i/o universal serial bus port [11:10] differential : these differential pairs are used to transmit data /address/command signals for ports 10 and 11. these ports can be routed to uhci controller #6 or the ehci controller #2. these ports can be optionally routed to ehci controller #1 when bit 0 rcba 35f0h is set. note: no external resistors are required on these signals. the ich10 integrates 15 k pull-downs and provides an output driver impedance of 45 which requires no exte rnal series resistor. oc0# / gpio59 oc1# / gpio40 oc2# / gpio41 oc3# / gpio42 oc4# / gpio43 oc5# / gpio29 oc6# / gpio30 oc7# / gpio31 oc8# / gpio44 oc9# / gpio45 oc10# / gpio46 oc11# / gpio47 i overcurrent indicators : these signals set corresponding bits in the usb controllers to indicate that an overcurrent condition has occurred. oc[11:0]# may optionally be used as gpios. note: oc[11:0]# are not 5 v tolerant. usbrbias o usb resistor bias: analog connection point fo r an external resistor. used to set transmit currents and intern al load resistors. usbrbias# i usb resistor bias complement: analog connection point for an external resistor. used to set transmit curr ents and internal load resistors. table 2-10. usb interface signals name typ e description http://www..net/ datasheet pdf - http://www..net/ signal description 58 datasheet 2.11 power management interface table 2-11. power management interface signals (sheet 1 of 3) name type description pltrst# o platform reset: the ich10 asserts pltrst# to reset devices on the platform (e.g., sio, fwh, lan, (g)mch, tpm, etc.). the ich10 asserts pltrst# during power-up and when s/w initiates a hard reset sequence through the reset control re gister (i/o register cf9h). the ich10 drives pltrst# inactive a minimum of 1 ms after both pwrok and vrmpwrgd are driven high. th e ich10 drives pltrst# active a minimum of 1 ms when initiated th rough the reset co ntrol register (i/o register cf9h). note: pltrst# is in the vccsus3_3 well. thrm# i thermal alarm: active low signal generate d by external hardware to generate an smi# or sci. thrmtrip# i thermal trip : when low, this signal indicates that a thermal trip from the processor occurred, and the ich10 will immediately transition to a s5 state. the ich10 will not wait for the processor stop grant cycle since the processor has overheated. slp_s3# o s3 sleep control: slp_s3# is for power plane control. this signal shuts off power to all non-critical systems when in s3 (suspend to ram), s4 (suspend to disk), or s5 (soft off) states. slp_s4# o s4 sleep control : slp_s4# is for power plane control. this signal shuts power to all non-critical systems when in the s4 (suspend to disk) or s5 (soft off) state. note: this pin must be used to cont rol the dram power in order to use the ich10?s dram power- cycling feature. refer to chapter 5.13.10.2 for details note: in a system with intel amt support , this signal should be used to control the dram power. in m1 state (where the host platform is in s3-s5 states an d the manageability sub-system is running) the signal is forc ed high along with slp_m# in order to properly maintain power to the dimm used for manageability sub-system. slp_s5# / gpio63 (corporate only) o s5 sleep control: slp_s5# is for power plane control. this signal is used to shut power off to all non-critical systems when in the s5 (soft off) states. ich10 corporate family: pin ma y also be used as gpio63. slp_m# o manageability sleep state control: this signal is used to control power planes to the intel amt sub- system. if no intel management engine firmware is present, slp_m# will have the same timings as slp_s3#. s4_state# / gpio26 o s4 state indication: this signal asserts low when the host platform is in s4 or s5 state. in platform s where the intel management engine is forcing the slp_s4# high along with slp_m#, this signal can be used by other devices on the board to know when the host platform is below the s3 state. http://www..net/ datasheet pdf - http://www..net/ datasheet 59 signal description pwrok i power ok: when asserted, pwrok is an indication to the ich10 that all power rails have been stable fo r 99 ms and that pciclk has been stable for 1 ms. pwrok can be dr iven asynchronously. when pwrok is negated, the ic h10 asserts pltrst#. note: 1. pwrok must deassert for a minimum of three rtc clock periods in order for the ich10 to fully reset the power and properly generate the pltrst# output. 2. pwrok must not glitch, even if rsmrst# is low. clpwrok i controller link power ok: when asserted, indi cates that power to the controller link subsystem (mch, ich, etc.) is stable and tells the ich to de-assert cl_rst# to the (g)mch. notes: 1. clpwrok must not assert before rsmrst# deasserts. 2. clpwrok must not asse rt after pwrok asserts. pwrbtn# i power button: the power button will cause smi# or sci to indicate a system request to go to a sleep stat e. if the system is already in a sleep state, this signal will cause a wake event. if pwrbtn# is pressed for more than 4 seconds, this will cause an unconditional transition (power button override) to the s5 state. override will occur even if the system is in the s1?s4 states. this signal has an internal pull-up resistor and has an internal 16 ms de-bounce on the input. ri# i ring indicate: this signal is an input from a modem. it can be enabled as a wake event, and this is preserved across power failures. sys_reset# i system reset : this pin forces an in ternal reset after being debounced. the ich10 will reset immediately if the smbus is idle; otherwise, it will wait up to 25 ms 2 ms for the smbus to idle before forcing a reset on the system. rsmrst# i resume well reset: this signal is used fo r resetting the resume power plane logic. this si gnal must be asserted for at least 10 ms after the suspend power wells are valid. wh en deasserted, this signal is an indication that the suspend power wells are stable. lan_rst# i lan reset: when asserted, the internal lan controller is in reset. this signal must be asserted until the lan power wells (vcclan3_3 and vcclan1_1) and vcccl3_3 power well are valid. when deasserted, this signal is an indication that the lan power wells are stable. notes: 1. lan_rst# must not deassert before rsmrst# deasserts 2. lan_rst# must not deas sert after pwrok asserts. 3. lan_rst# must not deassert until 1ms after the lan power wells (vcclan3_3 and vcclan1_1 and vcccl3_3 power well are valid. 4. if integrated lan is not used lan_rst# must be tied to vss. 5. lan_rst# must assert a mini mum of 20 ns before lan power rails become inactive. wake# i pci express* wake event: sideband wake signal on pci express asserted by components requesting wake up. mch_sync# i mch sync: this input is internally anded with the pwrok input. connect to the ich_sync# output of the (g)mch. table 2-11. power management in terface signals (sheet 2 of 3) name type description http://www..net/ datasheet pdf - http://www..net/ signal description 60 datasheet sus_stat# / lpcpd# / gpio61 (corporate only) o suspend status: this signal is asserted by the ich10 to indicate that the system will be entering a lo w power state soon. this can be monitored by devices wi th memory that need to switch from normal refresh to suspend refresh mode. it can also be used by other peripherals as an indication that th ey should isolate their outputs that may be going to powered-off planes. this signal is called lpcpd# on the lpc interface. ich10 corporate family: pin ma y also be used as gpio61. susclk / gpio62 (corporate only) o suspend clock: this clock is an output of the rtc generator circuit to use by other chips for refresh clock. ich10 corporate family: pin ma y also be used as gpio62. vrmpwrgd i vrm power good: this signal should be connected to the processor?s vrm power good signifying the vrm is stable. this signal is internally anded with the pwrok input. this signal is in the suspend well. drampwrok (corporate only) / gpio8 od o dram power ok: this signal should connect to the (g)mch?s ddr3_dram_pwrok pin. the ich asserts this pin to indicate when dram power is off. an external pull-up resistor is required. this pin is not open-drain when operating in gpio mode. ck_pwrgd o clock generator power good : this signal indicates to the clock generator when the main power well is valid. this signal is asserted high when both slp_s3# and vrmpwrgd are high. bmbusy# / gpio0 i bus master busy: this signal is used to support the c3 state. it indicates that a bus master device is busy. when this signal is asserted, the bm_sts bit will be set. if this signal goes active in a c3 state, it is treate d as a break event. note: this signal is internally sync hronized using the pciclk and a two-stage synchronizer. it does not need to meet any particular setup or hold time. signal may also be used as a gpio. stp_pci# / gpio15 o stop pci clock: this signal is an outp ut to the external clock generator for it to turn off the pci clock. it is used to support the c3 state. this signal can instead be used as a gpio. stp_cpu# / gpio25 (corporate only) o stop cpu clock: this signal is an output to the external clock generator for it to turn off the processor clock. corporate only: this signal ca n instead be used as a gpio. dprstp# o deeper stop: this is a copy of the dprslpvr and it is active low. dprslpvr / gpio16 o deeper sleep - voltage regulator: this signal is used to lower the voltage of the vrm during the c4 state. when the signal is high, the voltage regulator outputs the lower ?deeper sleep? vo ltage. when low (default), the voltage regulator ou tputs the higher ?normal? voltage. this signal can instead be used as a gpio. table 2-11. power management interface signals (sheet 3 of 3) name type description http://www..net/ datasheet pdf - http://www..net/ datasheet 61 signal description 2.12 processor interface table 2-12. processor interf ace signals (sheet 1 of 2) name type description a20m# o mask a20: a20m# will go active ba sed on either setting the appropriate bit in the port 92h re gister, or based on the a20gate input being active. ferr# i numeric coprocessor error: this signal is tied to the coprocessor error signal on the processor. ferr# is only used if the ich10 coprocessor error reporting functi on is enabled in the oic.cen register (chipset config registers:offset 31ffh: bit 1 for consumer family and offset 31feh: bit 9 for corporate family). if ferr# is asserted, the ich10 generates an internal irq13 to its interrupt controller unit. it is also used to gate the ignne# signal to ensure that ignne# is not asserted to the processor unless ferr# is active. ferr# requires an external weak pu ll-up to ensure a high level when the coprocessor error function is disabled. note: ferr# can be used in some st ates for notification by the processor of pending interrupt events. this functionality is independent of the oic register bit setting. ignne# o ignore numeric error: this signal is connected to the ignore error pin on the processor. ignne# is on ly used if the ich10 coprocessor error reporting function is enabled in the oic.cen register (chipset config registers:offset 31ffh: bit 1 for consumer family and offset 31feh: bit 9 for corporate family). if ferr# is active, indicating a coprocessor error, a write to the coprocessor error register (i/o register f0h) causes the ignne# to be asserted. ignne# remains asserted until ferr# is negated. if ferr# is not asserted when the coprocessor error register is writ ten, the ignne# signal is not asserted. init# o initialization: init# is asserted by the ich10 for 16 pci clocks to reset the processor. ich10 can be configured to support processor built in self test (bist). intr o cpu interrupt: intr is asserted by the ich10 to signal to the processor that an inte rrupt request is pending and needs to be serviced. it is an asynchronous output and normally driven low. nmi o non-maskable interrupt: nmi is used to force a non-maskable interrupt to the processor. the ich10 can generate an nmi when either serr# is asserted or ioch k# goes active via the serirq# stream. the processor detects an nm i when it detect s a rising edge on nmi. nmi is reset by setting the corresponding nmi source enable/ disable bit in the nmi status and co ntrol register (i/o register 61h). smi# o system management interrupt: smi# is an active low output synchronous to pciclk. it is assert ed by the ich10 in response to one of many enabled hardwa re or software events. stpclk# o stop clock request: stpclk# is an active low output synchronous to pciclk. it is asserted by the ich10 in response to one of many hardware or software events. wh en the processor samples stpclk# asserted, it responds by st opping its internal clock. http://www..net/ datasheet pdf - http://www..net/ signal description 62 datasheet 2.13 smbus interface rcin# i keyboard controller reset cpu: the keyboard controller can generate init# to the processor. this saves the external or gate with the ich10?s other sources of init#. when the ich10 detects the assertion of this signal , init# is generated for 16 pci clocks. note: the ich10 will ignore rcin# a ssertion during transitions to the s3, s4, and s5 states. a20gate i a20 gate: a20gate is from the keyboard controller. the signal acts as an alternative method to force the a20m# signal active. it saves the external or gate needed with various other chipsets. cpupwrgd o cpu power good: this signal should be connected to the processor?s pwrgood input to indica te when the processor power is valid. this is an output signal th at represents a logical and of the ich10?s pwrok and vrmpwrgd signals. dpslp# o deeper sleep: dpslp# is asserted by the ich10 to the processor. when the signal is low, the processor enters the deep sleep state by gating off the processor core cloc k inside the processor. when the signal is high (default), the processor is not in the deep sleep state. dpslp# o deeper sleep: dpslp# is asserted by th e ich10 to the processor. when the signal is low, the processor enters the deep sleep state by gating off the processor core cloc k inside the processor. when the signal is high (default), the processor is not in the deep sleep state. table 2-13. smbus interface signals name type description smbdata i/od smbus data: external pull-up resistor is required. smbclk i/od smbus clock: external pull-up re sistor is required. smbalert# / gpio11 / jtagtdo (corporate only) i smbus alert: this signal is used to wa ke the system or generate smi#. ich10 consumer family: this signal may be used as gpio11. ich10 corporate family: this sign al may be used as gpio11 or jtagtdo. table 2-12. processor interface signals (sheet 2 of 2) name type description http://www..net/ datasheet pdf - http://www..net/ datasheet 63 signal description 2.14 system management interface table 2-14. system management in terface signals (sheet 1 of 2) name type description intruder# i intruder detect: this signal can be set to disable system if box detected open. this signal?s status is readable, so it can be used like a gpio if the intruder detection is not needed. smlink[1:0] i/od system management link: smbus link to optional external system management asic or lan controller. external pull-ups are required. note that smlink0 corresponds to an smbus clock signal, and smlink1 corresponds to an smbus data signal. linkalert# / gpio60 / jtagrst# (corporate only) o od smlink alert: output of the integrated lan controller and input to either the integrated asf, intel amt or an external management controller in order for the lan?s smli nk slave to be serviced. external pull-up resistor is required. ich10 consumer: this signal can instead be used as a gpio60. ich10 corporate: this signal can instead be used as a gpio60 or jtagrst#. mem_led / gpio24 o od memory led: provides dram-powered led control. allows for the blinking of an led to indicate me mory activity in all power states. this functionality is configured and controlled by the intel management engine. this signal can instead be used as gpio24. http://www..net/ datasheet pdf - http://www..net/ signal description 64 datasheet 2.15 real time clock interface wol_en / gpio9 o wake on lan power enable . in an intel amt or asf enabled system, this output signal is driven high by the ich to control the lan subsystem power (vcclan3_3, vcccl3_3, lan phy power, and spi device) to support wake on lan (wol) when the intel management engine is powered off. this function ality is configured and controlled by the intel management engine pr ior to entering the powered off state. notes: 1. this signal should be or?d with the slp_m# signal on the motherboard to determine when to power the lan subsystem. 2. in order to support wol out of a g3 state, the wol_en pin needs to be pulled high by an external resistor until the intel management engine is initialized. if asf or intel amt are disabled on a board that is configured for wol_en support, bios must utiliz e gpio9 to control power to the lan subsystem when entering s3-s5. in platforms that do not support inte l amt or asf, this signal is used as gpio9. cpu_missing / gpio10 / jtagtms (corporate only) i cpu missing. this signal provides cpu missing functionality and is configured and controlled by the manageability engine. this signal must be connected to the cpu sktocc# output to indicate to the intel manageability engine that the cpu is not physically present when asserted. ich10 consumer family: this si gnal may be used as gpio10. ich10 corporate family: this sign al may be used as gpio10 or jtagtms. tpm_pp / gpio57 / jtagtck (corporate only) i tpm physical presence. this signal is asserted to indicate physical presence to the integrated tpm module. ich10 consumer family: this si gnal may be used as gpio57. ich10 corporate family: this sign al may be used as gpio57 or jtagtck. table 2-15. real time clock interface name type description rtcx1 special crystal input 1: this signal is connected to the 32.768 khz crystal. if no external crystal is used, then rt cx1 can be driven with the desired clock rate. rtcx2 special crystal input 2: this signal is connected to the 32.768 khz crystal. if no external crystal is used, then rtcx2 should be left floating. table 2-14. system management in terface signals (sheet 2 of 2) name type description http://www..net/ datasheet pdf - http://www..net/ datasheet 65 signal description 2.16 other clocks 2.17 miscellaneous signals table 2-16. other clocks name type description clk14 i oscillator clock: used for 8254 timers. runs at 14.31818 mhz. this clock is permitted to stop during s3 (or lower) states. clk48 i 48 mhz clock: used to run the usb contro ller. runs at 48.000 mhz. this clock is permitte d to stop during s3 (or lower) states. sata_clkp sata_clkn i 100 mhz differential clock: these signals are used to run the sata controller at 100 mhz. th is clock is permitted to stop during s3/s4/s5 states. dmi_clkp, dmi_clkn i 100 mhz differential clock: these signals are used to run the direct media interface. ru ns at 100 mhz. table 2-17. miscellaneous signals (sheet 1 of 2) name type description intvrmen i internal voltage regulator enable: this signal enables the internal vccsus1_1, vccsus 1_5 and vcccl1_5 regulators. this signal must be pulled-up to vccrtc. lan100_slp i internal voltage regulator enable: when connected to vccrtc, this signal enables the internal voltage regulators powering vcclan1_1 and vcccl1_1. this signal must be pulled-up to vccrtc. spkr o speaker: the spkr signal is the output of counter 2 and is internally ?anded? with port 61h bit 1 to provide speaker data enable. this signal drives an external speaker dr iver device, which in turn drives the system speaker. upon pltrst#, its output state is 0. note: spkr is sampled as a functional strap. see section 2.25.1 for more details. there is a weak in tegrated pull-down resistor on spkr pin. rtcrst# i rtc reset: when asserted, this signal resets register bits in the rtc well. notes: 1. unless cmos is be ing cleared (only to be done in the g3 power state), the rtcrst# input must always be high when all other rtc power planes are on. 2. in the case where the rtc battery is dead or missing on the platform, the rtcrst# pin must rise before the rsmrst# pin. http://www..net/ datasheet pdf - http://www..net/ signal description 66 datasheet 2.18 intel ? high definition audio link srtcrst# i secondary rtc reset: this signal resets the manageability register bits in the rtc well when the rtc battery is removed. notes: 1. the srtcrst# input must always be high when all other rtc power planes are on. 2. in the case where the rtc battery is dead or missing on the platform, the srtcrst# pin must rise before the rsmrst# pin. tp0 / gpio72 (corporate only) i test point 0: this signal must have an external pull-up to vccsus3_3. ich10 corporate: pin can instead be used as gpio72. tp3 i/o test point 3: route signal to a test point. tp4 i/o test point 4: route signal to a test point. tp5 i/o test point 5: route signal to a test point. tp6 i test point 6: route signal to a test point. tp7 o test point 7: route signal to a test point. table 2-18. intel ? high definition audio link signals name type description hda_rst# o intel ? high definition audio reset: master hardware reset to external codec(s). hda_sync o intel high definition audio sync: 48 khz fixed rate sample sync to the codec(s). also used to encode the stream number. note: this signal is sampled as a functional strap. see section 2.25.1 for more details. there is a weak integrated pull-down resistor on this pin. table 2-17. miscellaneous signals (sheet 2 of 2) name type description http://www..net/ datasheet pdf - http://www..net/ datasheet 67 signal description 2.19 serial peripheral interface (spi) hda_bit_clk o intel high definition audio bit clock output: 24.000 mhz serial data clock generated by the intel high definition audio controller (the intel ic h10). this signal has a weak internal pull- down resistor. hda_sdout o intel high definition audi o serial data out: serial tdm data output to the codec(s). this seri al output is double-pumped for a bit rate of 48 mb/s for in tel high definition audio. note: this signal is sampled as a functional strap. see section 2.25.1 for more details. there is a weak integrated pull-down resistor on this pin. hda_sdin[3:0] i intel high definition audio serial data in [3:0] : serial tdm data inputs from the codecs. the serial input is single-pumped for a bit rate of 24 mb/s for inte l high definition audio. these signals have integrated pull-down resistors, which are always enabled. note: during enumeration, the ich will drive this signal. during normal operation, the codec will drive it. table 2-19. serial peripher al interface (spi) signals name type description spi_cs0# o spi chip select 0 : used as the spi bus request signal. note: this signal is sampled as a functional strap. see section 2.25.1 for more details. spi_cs1# o spi chip select 1 : used as the spi bus request signal. note: this signal is sampled as a functional strap. see section 2.25.1 for more details. ther e is a weak integrated pull-up resistor on this pin. spi_miso i spi master in slave out : data input pin for ich10. spi_mosi o spi master out slave in : data output pin for ich10. note: this signal is sampled as a functional strap. see section 2.25.1 for more details. ther e is a weak integrated pull-down resistor on this pin. spi_clk o spi clock : spi clock signal, du ring idle the bus owner will drive the clock signal low. 17.86 mhz and 31.25 mhz. table 2-18. intel ? high definition audio link signals name type description http://www..net/ datasheet pdf - http://www..net/ signal description 68 datasheet 2.20 controller link 2.21 intel ? quiet system technology table 2-20. controller link signals signal name type description cl_clk0 i/o controller li nk clock 0 : bi-directional clock that connects to the (g)mch. cl_data0 i/o controller link data 0: bi-directional data that connects to the (g)mch. cl_vref0 i controller link re ference voltage 0: external reference voltage for controller link 0. ich10 corporate: when using in ternal reference voltage as configured by clinkvrefsel (i chstrp0:bit 5), an external circuit is not required and pin is no connect (recommended configuration). optionally, an external reference voltage generation circuit may be used (requires clinkvrefsel = 1). cl_rst0# o controller link reset 0: north controller link reset that connects to the (g)mch. table 2-21. intel ? quiet system technology signals signal name type description pwm[2:0] od o fan pulse width modulation outputs: pulse width modulated duty cycle output signal that is used for intel ? quiet system te c h n ol o g y. when controlling a 3-wire fan, this signal controls a power transistor that, in turn, cont rols power to the fan. when controlling a 4-wire fan, this sign al is connected to the ?control? signal on the fan. the polarity of this signal is programmable. the output default is low. these signals are 5v tolerant. tach0 /gpio17 tach1 /gpio1 tach2 /gpio6 tach3 /gpio7 i fan tachometer inputs: tachometer pulse input signal that is used to measure fan speed. this signal is connected to the ?sense? signal on the fan. can instead be used as a gpio. http://www..net/ datasheet pdf - http://www..net/ datasheet 69 signal description 2.22 jtag signals (intel ? ich10 corporate family only) note: jtag pin definitions are from ieee standard test acce ss port and boundary-scan architecture (ieee std. 1149.1-2001) sst i/o simple serial transport: single-wire, serial bus. connect to sst compliant devices such as sst thermal sensors or voltage sensors. peci i/o platform environment control interface: single-wire, serial bus. connect to corresponding pi n of the processor for accessing processor digita l thermometer. qst_bmbusy# (consumer only) / jtagtdi (corporate only) / gpio14 o intel qst bmbusy# interconnect (consumer only): this signal is used for intel ich10 consumer based platforms that support intel qst and c3 and/ or c4 processor states. qst_bmbusy# is asserted by th e ich10 to ensure that intel qst can read the processor thermal sensor since the sensor is inaccessible when the platform is in c3 or c4. qst_bmbusy# must be externally tied to the bmbusy# signal on the ich10 to cause the platform to exit or prevent entry into c3 or c4. qst_bmbusy# functionality is conf igured and controlled by the intel management engine firmware. ich10 consumer: in non-intel qst based platforms, this signal can instead be used as a gpio14. ich10 corporate: this signal is instead used as a gpio14 or jtagtdi. table 2-22. jtag signals name type description jtagtck (corporate only) / gpio57 / tpm_pp i/o test clock input (tck): the test clock input provides the clock for the jtag test logic. jtagtms (corporate only) / gpio10 / cpu_missing i/o test mode select (tms): the signal is decoded by the test access port (tap) controller to control test operations. jtagtdi (corporate only) / gpio14 / qst_bmbusy# i/o test data input (tdi): serial test instru ctions and data are received by the test logic at tdi. jtagtdo (corporate only) / gpio11/ smbalert# i/o test data output (tdo): tdo is the serial output for test instructions and data from the test logic defined in this standard. jtagrst# (corporate only) / linkalert# / gpio60 i/o test reset (rst): rst is an active low asynchronous signal that can reset the test access port (tap) controller. note: the rst signal is optional per the ieee 114.1 specification, and is not fu nctional for boundary scan te s t i n g table 2-21. intel ? quiet system technology signals signal name type description http://www..net/ datasheet pdf - http://www..net/ signal description 70 datasheet 2.23 general purpose i/o signals table 2-23. general purpose i/o signals (sheet 1 of 3) name type tolerance power well default description gpio72 (corporate only) i/o 3.3 v core native ich10 consumer family: pin implemented as tp0 only. ich10 corporate family: pin is multiplexed with tp0. (note 13) gpio63 (corporate only) i/o 3.3 v suspend native ich10 consumer family: pin may only be used as slp_s5#. ich10 corporate family: pin is multiplexed with slp_s5# (note 13) gpio62 (corporate only) i/o 3.3 v suspend native ich10 consumer family: pin may only be used as susclk ich10 corporate family: pin is multiplexed with susclk (note 13) gpio61 (corporate only) i/o 3.3 v suspend native ich10 consumer family: pin may only be used as sus_stat# / lpcpd# ich10 corporate family: pin is multiplexed with sus_stat# / lpcpd# (note 13) gpio60 i/o 3.3 v suspend native ich10 consumer family: multiplexed with linkalert#. ich10 corporate family: multiplexed with linkalert# and jtagrst#. (note 13) gpio59 i/o 3.3 v suspend native multiplexed with oc[0]#. (note 13) gpio57 i/o 3.3 v suspend gpi ich10 consumer family: can be used as tpm_pp. ich10 corporate family can be used as tpm_pp or jtagtck. gpio56 i/o 3.3 v suspend gpi unmultiplexed gpio55 i/o 3.3 v core native multi plexed with gnt3# (note 8). gpio54 i/o 5.0 v core native multiplexed with req3#. (note 13) gpio53 i/o 3.3 v core native multi plexed with gnt2# (note 8). gpio52 i/o 5.0 v core native multiplexed with req2#. (note 13) gpio51 i/o 3.3 v core native multi plexed with gnt1# (note 8). gpio50 i/o 5.0 v core native multiplexed with req1#. (note 13) gpio49 i/o 3.3v core gpo unmultiplexed (note 8). gpio48 i/o 3.3 v core gpi mul tiplexed with sdataout1. gpio[47:44] i/o 3.3v suspend native multiplexed with oc[11:8]#. (note 13) gpio[43:40] i/o 3.3 v suspend native multiplexed with oc[4:1]#. (note 13) gpio39 i/o 3.3 v core gpi multiplexed with sdataout0. gpio38 i/o 3.3 v core gpi multiplexed with sload. gpio37 i/o 3.3 v core gpi multiplexed with sata3gp. gpio36 i/o 3.3 v core gpi multiplexed with sata2gp. http://www..net/ datasheet pdf - http://www..net/ datasheet 71 signal description gpio35 i/o 3.3 v core gpo multiplexed with sataclkreq#. gpio34 i/o 1.5 v / 3.3 v (note 12) vcchda gpo unmultiplexed. gpio33 i/o 3.3 v core gpo unmultiplexed. gpio32 i/o 3.3 v core gpo unmultiplexed. gpio31 i/o 3.3 v suspend native multiplexed with oc7#. (note 13) gpio30 i/o 3.3 v suspend native multiplexed with oc6#. (note 13) gpio29 i/o 3.3 v suspend native multiplexed with oc5#. (note 13) gpio28 i/o 3.3 v suspend gpo unmultiplexed. gpio27 i/o 3.3 v suspend gpo unmultiplexed gpio26 i/o 3.3 v suspend native multip lexed with s4_state#. (note 9) gpio25 (corporate only) i/o 3.3 v suspend native defaul t as stp_cpu# (note 3). gpio24 i/o 3.3 v suspend gpo can be used as mem_led. gpio24 configuration register bits are not cleared by cf9h reset event. gpio23 i/o 3.3 v core native multiplexed with ldrq1#. (note 13) gpio22 i/o 3.3 v core gpi multiplexed with sclock. gpio21 i/o 3.3 v core gpi multiplexed with sata0gp. gpio20 i/o 3.3 v core gpo unmultiplexed. (note 8) gpio19 i/o 3.3 v core gpi multiplexed with sata1gp. gpio18 i/o 3.3 v core gpo (note 11) unmultiplexed. gpio17 i/o 3.3 v core gpi multiplexed with tach0. gpio16 i/o 3.3 v core native may also be used as dprslpvr gpio15 i/o 3.3 v suspend native default as stp_pci#. (note 3) gpio14 i/o 3.3 v suspend gpi ich10 consumer family: can be used as qst_bmbusy#. ich10 corporate family: can be used as jtagtd, or qst_bmbusy#i. gpio13 i/o 3.3 v suspend gpi unmultiplexed. gpio12 i/o 3.3 v suspend gpo multiplexed with lan_phy_pwr_ctrl. (note 13) gpio11 i/o 3.3 v suspend native ich10 consumer family: can be used as smbalert#. (note 13) ich10 corporate family can be used as smbalert# or jtagtdo. (note 13) gpio10 i/o 3.3 v suspend gpi ich10 consumer family: can be used as cpu_missing. ich10 corporate family: can be used as cpu_missing or jtagtms. table 2-23. general purpose i/o signals (sheet 2 of 3) name type tolerance power well default description http://www..net/ datasheet pdf - http://www..net/ signal description 72 datasheet notes: 1. all gpios can be configured as either input or output. 2. gpi[15:0] can be configured to cause a smi# or sci. note that a gpi can be routed to either an smi# or an sci, but not both. 3. some gpios exist in the vccsus3_3 power plan e. care must be take n to make sure gpio signals are not driven high into powered-down planes. also, ex ternal devices should not be driving powered down gpios high. some ic h10 gpios may be connected to pins on devices that exist in the core well. if these gpios are outputs, there is a danger that a loss of core power (pwrok low) or a power button overri de event will result in the intel ich10 driving a pin to a logic 1 to anot her device that is powered down. 4. the functionality that is multiplexed with the gpio may not be utilized in desktop configuration. 5. this gpio is not an open-drain when configured as an output. 6. spi_cs1# is located in the vcccl3_3 well. 7. when this signal is configured as gpo the output stage is an open-drain. 8. this signal is sampled as a functional strap. see section 2.25.1 for more details. 9. the gpio_use_sel bit for this signal is ov erridden by bit 8 in the gen_pmcon_3 register (d31:f0). 10. the gpio_use_sel bit for this is ignored. functionality is set by bits 9:8 of flmap0 register. 11. gpio18 will toggle at a frequency of appr oximately 1 hz when the ich10 comes out of reset. 12. the tolerance of this pin is determined by the voltage of vcchda either 3.3 v or 1.5 v. 13. when the multiplexed gpio is used as gpio functionality, ca re should be taken to ensure the signal is stable in its inactive state of the native functionality, immediately after reset until it is initialized to gpio functionality. gpio9 i/o 3.3 v suspend native can be used as wol_en. gpio8 i/o 3.3 v suspend corporate only gpi consumer only native ich10 corporate family: can be used as drampwrok. ich10 consumer family: unmultiplexed gpio[7:6] i/o 3.3 v core gpi multiplexed with tach[3:2]. gpio[5:2] i/od 5 v core gpi multiplexed with pirq[h:e]# (note 6). gpio1 i/o 3.3 v core gpi multiplexed with tach1. gpio0 i/o 3.3 v core gpi multiplexed with bmbusy#. table 2-23. general purpose i/o signals (sheet 3 of 3) name type tolerance power well default description http://www..net/ datasheet pdf - http://www..net/ datasheet 73 signal description 2.24 power and ground signals table 2-24. power and ground signals (sheet 1 of 2) name description v5ref reference for 5 v tolerance on core well inputs. this power may be shut off in s3, s4, s5 or g3 states. v5ref_sus reference for 5 v tolerance on suspend we ll inputs. this power is not expected to be shut off unless the system is unplugged. vcc1_1 1.1 v supply for core well logic. this powe r may be shut off in s3, s4, s5 or g3 states. vcc1_5_a 1.5 v supply for logic and i/o. this power may be shut off in s3, s4, s5 or g3 states. vcc1_5_b 1.5 v supply for logic and i/o. this power may be shut off in s3, s4, s5 or g3 states. vcc3_3 3.3 v supply for core well i/o buffers. th is power may be shut off in s3, s4, s5 or g3 states. vcccl1_1 1.1v supply for controller link. this pl ane must be on in s0 and other times controller link is used. this voltage is generated internally (see section 2.25.1 for strapping option) and, this pin can be left as no co nnect unless decoupling is required. vcccl1_5 1.5v supply for controller link. this pl ane must be on in s0 and other times controller link is used. this voltage is generated internally (see section 2.25.1 for strapping option), and this pin can be left as no co nnect unless decoupling is required. vcccl3_3 3.3v supply for controller link. this is a separate power plane that may or may not be powered in s3?s5 states. this plane must be on in s0 and other times controller link is used. note: vcccl3_3 must always be powe red when vcclan3_3 is powered. vccdmi power supply for dmi. 1.05v, 1.25v or 1.5v depending on (g)mch?s dmi voltage. vccdmipll 1.5 v supply for core well lo gic. this signal is used for the dmi pll. this power may be shut off in s3, s4, s5 or g3 states. vccglan1_5 1.5v supply for integrated gigabit lan i/o buffers. this power is on in s0 and is turned of in s3, s4, s5, even it integrated gigabit lan is not used. vccglan3_3 3.3v supply for integrated gigabit lan lo gic and i/o. this po wer is on in s0 and is turned of in s3, s4, s5, even it integrated gigabit lan is not used. vccglanpll 1.5v supply for core well logic. this si gnal is used for the integrated gigabit lan pll. this power is shut of f in s3, s4, s5 and g3 states. vcchda core supply for intel high de finition audio. this pin ca n be either 1.5 or 3.3 v. this power may be shut off in s3, s4, s5 or g3 states. note: vccsushda and vcchda can be conn ected to either 1.5 v or 3.3 v supplies, but both pins must be connected to supplies that are the same nominal value. vcclan1_1 1.1 v supply for lan controller logic. th is is a separate power plane that may or may not be powered in s3?s5 states. this voltage is generated internally (see section 2.25.1 for strapping option) and, these pins can be le ft as no connec t unless decoupling is required. http://www..net/ datasheet pdf - http://www..net/ signal description 74 datasheet vcclan3_3 3.3 v supply for lan connect interface bu ffers. this is a separate power plane that may or may not be powered in s3?s5 states. this plane mu st be on in s0. note: vcclan3_3 must always be powered when vcccl3_3 or vcc3_3 is powered. vccrtc 3.3 v (can drop to 2.0 v min. in g3 st ate) supply for the rt c well. this power is not expected to be shut off unless the rtc battery is removed or completely drained. note: implementations should not attempt to clear cmos by using a jumper to pull vccrtc low. clearing cmos in an intel ich10-based platform can be done by using a jumper on rtcrst# or gpi. vccsatapll 1.5 v supply for core well logic. this si gnal is used for the sata pll. this power may be shut off in s3, s4, s5 or g3 states. must be powered even if sata is not used. vccsus1_1 1.1 v supply for suspend well logic. this power is not expected to be shut off unless the system is unplugged. this voltage is generated internally (see section 2.25.1 for strapping option). these pins can be left as no conn ects unless decoupling is required. vccsus1_5 1.5v supply for the suspend well i/o. this power is not expected to be shut off unless the system is unplugged. this voltage is generated internally (see section 2.25.1 for strapping option). these pins can be left as no conn ects unless decoupling is required. vccsus3_3 3.3 v supply for suspend well i/o buffers . this power is not expected to be shut off unless the system is unplugged. vccsushda suspend supply for intel ? high definition audio. this pin can be either 1.5 or 3.3 v. t note: vccsushda and vcchda can be conn ected to either 1.5 v or 3.3 v supplies, but both pins must be connected to supplies that are the same nominal value. vccusbpll 1.5 v supply for core well lo gic. this signal is used for the usb pll. this power may be shut off in s3, s4, s5 or g3 st ates. must be powere d even if usb not used. vss grounds. v_cpu_io powered by the same supply as the processor i/o voltag e. this supply is used to drive the processor inte rface signals listed in ta b l e 2 - 1 2 . table 2-24. power and ground signals (sheet 2 of 2) name description http://www..net/ datasheet pdf - http://www..net/ datasheet 75 signal description 2.25 pin straps 2.25.1 functional straps the following signals are used for static configuration. they are sampled at the rising edge of pwrok to select configurations (excep t as noted), and then revert later to their normal usage. to invoke the associated mode, the signal should be driven at least four pci clocks prior to the time it is sampled. the ich10 has implemented soft straps. soft straps are used to configure specific functions within the ich and (g)mch very earl y in the boot process before bios or sw intervention. when descriptor mode is enable d, the ich will read soft strap data out of the spi device prior to the de-assertion of reset to both the intel management engine and the host system. refer to section 5.23.2 for information on descriptor mode and section for more information on soft straps and their settings. table 2-25. functional strap definitions (sheet 1 of 4) signal usage when sampled comment hda_sdout xor chain entrance rising edge of pwrok allows entrance to xor chain testing when tp3 pulled low at rising edge of pwrok. hda_sdout pci express* port config 1 bit 1 (port 1-4) (consumer only) rising edge of pwrok when tp3 not pulled low at rising edge of pwrok, sets bit 1 of rpc.pc (chipset config registers:offset 224h).this signal has a weak internal pull-down. hda_sync (consumer only) pci express port config 1 bit 0 (port 1-4) rising edge of pwrok this signal has a weak internal pull-down. sets bit 0 of rpc.pc (chipset config registers:offset 224h) gnt2# / gpio53 (consumer only) pci express port config 2 bit 2 (port 5-6) rising edge of pwrok this signal has a we ak internal pull-up. sets bit 2 of rpc.pc2 (chipset config registers:offset 0224h) when sampled low. gpio20 reserved rising edge of pwrok this signal has a weak internal pull-down. note: this signal should not be pulled high gnt1#/gpio51 esi strap (server/ workstation only) rising edge of pwrok tying this strap low configures dmi for esi- compatible operation. this signal has a weak internal pull-up. note: esi compatible mode is for server platforms only. this signal should not be pulled low for desktop. gnt3# / gpio55 to p - b l o c k swap override rising edge of pwrok the signal has a weak internal pull-up. if the signal is sampled low, this indicates that the system is strapped to the ?top- block swap? mode (intel ich10 inverts a16 for all cycles targeting bios space). the status of this strap is readable via the top swap bit (chipset config registers:offset 3414h:bit 0). note that software will not be able to clear the top-swap bit until the system is rebooted without gnt3# being pulled down. http://www..net/ datasheet pdf - http://www..net/ signal description 76 datasheet gnt0# boot bios destination selection 0 rising edge of pwrok this field determines the destination of accesses to the bi os memory range. signals have weak inte rnal pull-ups. also controllable via boot bios destination bit (chipset config registers:offset 3410h:bit 11). this strap is used in conjunction with boot bios destination selection 1 strap. note: if option 11 lpc is selected, bios may still be placed on lpc, but all platforms with ich10 (corporate only) require spi flash connected directly to the ich's spi bus with a valid descriptor in order to boot. note: booting to pci is intended for debut/testing only. boot bios destination select to lpc/pci by functional strap or via boot bios destination bit will not affect spi accesses initiated by intel management engine or integrated gbe lan. table 2-25. functional strap definitions (sheet 2 of 4) signal usage when sampled comment bit11 bit 10 boot bios destination 01 spi 10 pci 11 lpc 00 reserved http://www..net/ datasheet pdf - http://www..net/ datasheet 77 signal description spi_cs1# boot bios destination selection 1 rising edge of clpwrok this field determines the destination of accesses to the bi os memory range. signals have weak inte rnal pull-u ps. also controllable via boot bios destination bit (chipset config registers:offset 3410h:bit 10). this strap is used in conjunction with boot bios destination selection 0 strap. note: if option 11 lpc is selected bios may still be placed on lpc, but all platforms with ich10 (corporate only) require spi flash connected directly to the ich's spi bus with a valid descriptor in order to boot. note: booting to pci is intended for debut/testing on ly. boot bios destination select to lpc/pci by functional strap or via boot bios destination bit will not affect spi accesses initiated by intel management engine or integrated gbe lan. sataled# (consumer only) pci express lane reversal (lanes 1-4) rising edge of pwrok signal has weak internal pull-up. sets bit 27 of mpc.lr (device 28: function 0: offset d8) spkr no reboot rising edge of pwrok the signal has a weak internal pull-down. if the signal is sampled high, this indicates that the system is strapped to the ?no reboot? mode (ich10 will disable the tco timer system reboot fe ature). the status of this strap is readable via the no reboot bit (chipset config registers:offset 3410h:bit 5). tp3 xor chain entrance rising edge of pwrok see intel ? ich10 family xor chains in- circuit tester package for functionality information. this signal has a weak internal pull-up. note: this signal should not be pulled low unless using xo r chain testing. table 2-25. functional strap definitions (sheet 3 of 4) signal usage when sampled comment bit11 bit 10 boot bios destination 01 spi 10 pci 11 lpc 00 reserved http://www..net/ datasheet pdf - http://www..net/ signal description 78 datasheet note: see section 3.1 for full details on pull-up/pull-down resistors. gpio33 / hda_dock_en# flash descriptor security override strap rising edge of pwrok if sampled low, the flash descriptor security will be overridden. if high, the security measures de fined in the flash descriptor will be in effect. note: this strap should only be enabled in manufacturing environments using an external pull-down resistor. note: asserting the gpio33 low on the rising edge of pwrok will also disable intel management engine and intel manage ment engine features. gpio49 dmi te r m i n a t i o n voltage rising edge of pwrok this signal has a we ak internal pull-up. note: when dmi is dc coupled this signal should not be pulled low during the time the strap is sampled. note: when dmi is ac coupled, this signal should be pulled low during the time the strap is sampled. spi_mosi (corporate only) integrated tpm enable rising edge of clpwrok this signal has a weak internal pull-down resistor. when the signal is sampled low the integrated tpm will be disabled. when the signal is sampled hi gh, the (g)mch tpm enable strap is sampled low and the tpm disable bit is clear, the integrated tpm will be enabled. note: for consumer applications this signal is required to be floating or pulled low. table 2-25. functional strap definitions (sheet 4 of 4) signal usage when sampled comment http://www..net/ datasheet pdf - http://www..net/ datasheet 79 signal description 2.25.2 external rtc circuitry the ich10 implements an internal oscillator circuit that is sensitive to step voltage changes in vccrtc. figure 2-1 shows an example schematic recommended to ensure correct operation of the ich10 rtc. note: c1 and c2 depend on crystal load. figure 2-1. example external rtc circuit 32.768 khz xtal 10m vccrtc rtcx2 rtcx1 vbatt 1uf 1 k 3.3v sus c1 c2 r1 rtcrst# 1.0 uf 20 k 0.1uf srtcrst# 20 k 1.0 uf schottky diodes http://www..net/ datasheet pdf - http://www..net/ signal description 80 datasheet http://www..net/ datasheet pdf - http://www..net/ datasheet 81 intel ? ich10 pin states 3 intel ? ich10 pin states 3.1 integrated pull-ups and pull-downs notes: 1. simulation data shows that these resistor values can range from 10 k to 40 k . 2. simulation data shows that these resistor values can range from 9 k to 50 k . table 3-1. integrated pull -up and pull-down resistors signal resistor type nominal value notes cl_clk0 pull-up 20 k 13 cl_data0 pull-up 20 k 13 cl_rst0# pull-up 10 k 4 dprslpvr/gpio16 pull-down 20 k 2, 10 hda_bit_clk pull-down 20 k 1, 9 hda_dock_en#/gpio33 pull-up 20 k 3,7 hda_rst# pull-down 20 k 2 hda_sdin[3:0] p ull-down 20 k 2 hda_sdout pull-down 20 k 2, 7 hda_sync pull-down 20 k 2, 7 glan_dock# pull-up pull-down 20 k 20 k 3, 14 gnt0#, gnt[3:1]#/gpio[55,53,51] pull-up 20 k 3, 11, 12 gpio20 pull-down 20 k 3, 7 gpio49 pull-up 20 k 3, 7 lad[3:0]# / fhw[3:0]# pull-up 20 k 3 lan_rxd[2:0] pull-up 20 k 4 ldrq0 pull-up 20 k 3 ldrq1 / gpio23 pull-up 20 k 3 pme# pull-up 20 k 3 pwrbtn# pull-up 20 k 3 sataled# pull-up 15 k 8 spi_cs1# pull-up 20 k 3, 10 spi_mosi pull-down 20 k 3, 7 spi_miso pull-up 20 k 3 spkr pull-down 20 k 2 tach[3:0] pull-up 20 k 3 tp3 pull-up 20 k 6 usb[11:0] [p,n] pull-down 15 k 5 http://www..net/ datasheet pdf - http://www..net/ intel ? ich10 pin states 82 datasheet 3. simulation data shows that these resistor values can range from 15 k to 35 k . 4. simulation data shows that these resistor values can range from 7.5 k to 16 k . 5. simulation data shows that these resistor values can range from 14.25 k to 24.8 k 6. simulation data shows that these resistor values can range from 10 k to 30 k . 7. the pull-up or pull-down on this signal is on ly enabled at boot/reset for strapping function. 8. simulation data shows that these resistor values can range from 10 k to 20 k . the internal pull-up is only enab led during pltrst# assertion. 9. the pull-down on this signal is only enabled when in s3. 10. the pull-up or pull-dow n on this signal is on ly enabled during reset. 11. the pull-up on this signal is not enabled when pcirst# is high. 12. the pull-up on this signal is not enabled when pwrok is low. 13. simulation data shows that these resistor values can range from 15 k to 31 k . 14. the pull-up or pull-down on this pin is only active when configured for native glan_dock# functionality and is de termined by the lan controller. http://www..net/ datasheet pdf - http://www..net/ datasheet 83 intel ? ich10 pin states 3.2 output and i/o signals planes and states ta b l e 3 - 2 shows the power plane associated with the output and i/o signals, as well as the state at various times. within the table, the following terms are used: ?high-z? tri-state. ich10 not driving the signal high or low. ?high? ich10 is driving the signal to a logic 1. ?low? ich10 is driving th e signal to a logic 0. ?defined? driven to a level that is defi ned by the function or external pull- up/pull-down resistor (will be high or low). ?undefined? ich10 is driving the sign al, but the value is indeterminate. ?running? clock is toggling or signal is transitioning because function not stopping. ?off? the power plane is off; ich10 is not driving when configured as an output or sampling when configured as an input. ?input? ich10 is sampling and signal state determined by external driver. note: signal levels are the same in s4 and s5, except as noted. the ich10 suspend well signal states are in determinate and undefined and may glitch prior to rsmrst# deassertion. this does not apply to lan_rst# , slp_s3#, slp_s4#, s4_state# and slp_s5#. these signals are determinate and defined prior to rsmrst# deassertion. the ich10 core well signal states are indete rminate and undefined and may glitch prior to pwrok assertion. this does not apply to ferr# and thrmtrip#. these signals are determinate and defined prior to pwrok assertion. table 3-2. power plane and states for output and i/o signals for co nfigurations (sheet 1 of 5) signal name power plane during reset 4 immediately after reset 4 c3/c4 s1 s3 s4/s5 pci express* petp[5:1], petn[5:1], petp6 / glantxp, petn6 / glantxn core high high 8 defined off off dmi dmi[3:0]txp, dmi[3:0]txn core high high defined off off pci bus ad[31:0] core low undefined defined off off c/be[3:0]# core low undefined defined off off devsel# core high-z high-z high-z off off frame# core high-z high-z high-z off off gnt0# 11 , gnt[3:1]# 11 / gpio[55, 53, 51] core high-z high high off off irdy#, trdy# core high-z high-z high-z off off http://www..net/ datasheet pdf - http://www..net/ intel ? ich10 pin states 84 datasheet par core low undefined defined off off pcirst# suspend low high high low low perr# core high-z high-z high-z off off plock# core high-z high-z high-z off off stop# core high-z high-z high-z off off lpc interface lad[3:0] / fwh[3:0] core high high high off off lframe# / fwh[4] core high high high off off lpcpd# / sus_stat# / gpio61 (corporate only) suspend low high high low low firmware hub init3_3v# core high high high off off lan connect interface lan_rstsync lan high low defined defined defined lan_txd[2:0] lan low low defined defined defined gigabit lan connect interface glan_txp / petp6, glan_txn / petn6 glan high high defined off off lan_rstsync lan high low defined defined defined sata interface sata[5:0]txp, sata[5:0]txn core high-z high-z defined off off sataled# 11 core high-z high-z defined off off satarbias core high-z high-z defined off off sataclkreq# / gpio35 core low low defined off off sclock/gpio22 core input input defined off off sload/gpio38 core input input defined off off sdataout[1:0]/ gpio[48,39] core input input defined off off interrupts pirq[a:d]#, core high-z high-z high-z off off pirq[h:e]# / gpio[5:2] core input input defined off off serirq core high-z high-z high-z off off usb interface usb[11:0][p,n] suspend low low defined defined defined usbrbias suspend high-z high-z defined defined defined power management dprslpvr core low low high off off table 3-2. power plane and states for output and i/o signals for configurations (sheet 2 of 5) signal name power plane during reset 4 immediately after reset 4 c3/c4 s1 s3 s4/s5 http://www..net/ datasheet pdf - http://www..net/ datasheet 85 intel ? ich10 pin states dprstp# cpu high high high off off pltrst# suspend low high high low low slp_m# 9 suspend low high high defined defined slp_s3# suspend low high high low low slp_s4# suspend low high high high defined s4_state# / gpio26 suspend low defined defined defined defined slp_s5#/ gpio63 (corporate only) suspend low high high high low 6 sus_stat# / lpcpd# / gpio61 (corporate only) suspend low high high low low susclk suspend low running ck_pwrgd suspend low high high low low stp_pci# / gpio15 suspend high high defined defined defined stp_cpu# / gpio25 (corporate only) suspend high high defined defined defined corporate only: drampwrok / gpio8 suspend low low defined defined defined/ low 12 defined/ low 12 processor interface dpslp# cpu high high high off off a20m# cpu dependant on a20gate signal see note 1 high off off cpupwrgd cpu low 3 high high off off ignne# cpu high see note 1 high off off init# cpu high high high off off intr cpu see note 5 see note 5 low off off nmi cpu see note 5 see note 5 low off off smi# cpu high high high off off stpclk# cpu high high low off off smbus interface smbclk, smbdata suspend high-z high-z defined defined defined system management interface mem_led / gpio24 suspend low low defined defined defined cpu_missing / gpio10 / jtagtms (corporate only) suspend input input defined defined defined gpio14 / jtagtdi (corporate only) / qst_bmbusy# suspend input input defined defined defined wol_en / gpio9 suspend high-z high-z defined defined defined table 3-2. power plane and states for output and i/o signals for co nfigurations (sheet 3 of 5) signal name power plane during reset 4 immediately after reset 4 c3/c4 s1 s3 s4/s5 http://www..net/ datasheet pdf - http://www..net/ intel ? ich10 pin states 86 datasheet linkalert# / gpio60 / jtagrst# (corporate only) suspend high-z high-z defined defined defined tpm_pp / gpio57 / jtagtck (corporate only) suspend input input defined defined defined spi_cs[1]# 11 suspend high high defined defined defined smlink[1:0] suspend high-z hi gh-z defined defined defined miscellaneous signals spkr 11 core high-z low defined off off intel ? high definition audio interface hda_rst# hda suspend low low 7 defined low low hda_sdout 11 hda low low low off off hda_sync hda low low low off off hda_bit_clk hda low low low off off unmultiplexed gpio signals gpio0 / bmbusy# core input input defined off off consumer only: gpio8 suspend input input defined defined defined gpio12 / lan_phy_pwr_ctrl suspend low low defined defined defined gpio13 suspend input input defined defined defined gpio16/dprslpvr core low low defined off off gpio18 core high see note 2 defined off off gpio20 11 core low high defined off off gpio[28:27] suspend low low defined defined defined gpio33 11 , gpio32 core high high defined off off gpio34 hda low low defined off off gpio49 11 core high high defined off off gpio56 suspend input input defined defined defined spi interface spi_cs0# controller link high high defined defined defined spi_cs1# 11 controller link high high defined defined defined spi_mosi 11 controller link low low defined defined defined spi_clk controller link low low running defined defined controller link cl_clk0 controller link low low defined 10 defined 10 defined 10 table 3-2. power plane and states for output and i/o signals for configurations (sheet 4 of 5) signal name power plane during reset 4 immediately after reset 4 c3/c4 s1 s3 s4/s5 http://www..net/ datasheet pdf - http://www..net/ datasheet 87 intel ? ich10 pin states notes: 1. ich10 drives these signals hi gh after the processor reset 2. gpio[18] will toggle at a frequency of a pproximately 1 hz when the ich10 comes out of reset 3. cpupwrgd represents a logical and of th e ich10?s vrmpwrgd and pwrok signals, and thus will be driven low by ich10 when eith er vrmpwrgd or pwrok are inactive. during boot, or during a hard reset wi th power cycling, cpupwrgd will be expected to transition from low to high-z. 4. the states of core and proc essor signals are evaluated at the times during pltrst# and immediately after pltrst #. the states of the lan and gl an signals are evaluated at the times during lan_rst# and immediately after lan_rst#. the states of the controller link signals are taken at th e times during cl_r st# and immediately after cl_rst#. the states of the suspend signals are evaluated at the times during rsmrst# and immediately after rsmrst#. th e states of the hda signals are evaluated at the times during hda_rst# and imme diately after hda_rst#. 5. ich10 drives these signals low before pwro k rising and low afte r the processor reset. 6. slp_s5# signals will be high in the s4 state. 7. low until intel high definition audio controller reset bit set (d27:f0:offset hdbar+08h:bit 0), at which time hda_rst# will be high and hda_bit_clk will be running. 8. petp/n[6:1] high until port is enabled by software. 9. the slp_m# state will be determined by intel amt policies. 10. the state of signals in s3-5 will be define d by intel amt policies. 11. this signal is sampled as a functional strap during reset. 12. the state of drampwrok during s3/s4/s5 is dependent on the slp_s4# and clpwrok signals. cl_data0 controller link low low defined 10 defined 10 defined 10 cl_rst0# suspend low high defined 10 defined 10 defined 10 intel ? quiet system technology pwm[2:0] core high-z low defined off off sst controller link high-z low defined off off peci cpu high-z low defined off off table 3-2. power plane and states for output and i/o signals for co nfigurations (sheet 5 of 5) signal name power plane during reset 4 immediately after reset 4 c3/c4 s1 s3 s4/s5 http://www..net/ datasheet pdf - http://www..net/ intel ? ich10 pin states 88 datasheet 3.3 power planes for input signals ta b l e 3 - 3 shows the power plane associated with each input signal, as well as what device drives the signal at various times. valid states include: high low static: will be high or low, but will not change driven: will be high or low, and is allowed to change running: for input clocks the ich10 suspend well signal states are in determinate and undefined and may glitch prior to rsmrst# deassertion. this does not apply to lan_rst#, slp_s3#, slp_s4#, s4_state# and slp_s5#. these signals are determinate and defined prior to rsmrst# deassertion. the ich10 core well signal states are indeterminate and undefined and may glitch prior to pwrok assertion. this does not apply to ferr# and thrmtrip#. these signals are determinate and defined prior to pwrok assertion. table 3-3. power plane for input signals for configurations (sheet 1 of 3) signal name power well driver during reset c3/c4 s1 s3 s4/s5 dmi dmi_clkp, dmi_clkn core clock generator running off off dmi[3:0]rxp, dmi[3:0]rxn core (g)mch driven off off pci express* perp[5:1], pern[5:1], perp6 / glan_rxp, pern6 / glan_rxn core pci express* device driven off off pci bus req0#, req1# / gpio50 1 req2# / gpio52 1 req3# / gpio54 1 core external pull-up driven off off pciclk core clock generator running off off pme# suspend internal pull-up driven driven driven serr# core pci bus peripherals high off off lpc interface ldrq0# core lpc devices high off off ldrq1# / gpio23 1 core lpc devices high off off lan connect interface glan_clk suspend lan connect component driven off off lan_rxd[2:0] suspend lan connect component driven driven driven http://www..net/ datasheet pdf - http://www..net/ datasheet 89 intel ? ich10 pin states gigabit lan connect interface glan_rxp / perp6, glan_rxn / pern6 suspend gigabit lan connect component driven off off sata interface sata_clkp, sata_clkn core clock generator running off off sata[5:0]rxp, sata[5:0]rxn core sata drive driven off off satarbias# core external pull-down driven off off sata[5:4]gp sata[3:0]gp / gpio[37, 36, 19, 21] 1 core external device or external pull-up/pull- down driven off off usb interface oc0# / gpio59, oc[4:1]# / gpio[43:40], oc[7:5]# / gpio [31:29], oc[11:8]# / gpio[47:44] suspend external pull-ups driven driven driven usbrbias# suspend external pull-down driven driven driven power management bmbusy# /gpio0 1 core graphics component [(g)mch] driven high off clpwrok suspend external circuit driven driven driven lan_rst# suspend external circuit high high high mch_sync# core (g)mch driven off off pwrbtn# suspend internal pull-up driven driven driven pwrok rtc system power supply driven off off ri# suspend serial port buffer driven driven driven rsmrst# rtc external rc circuit high high high sys_reset# suspend external circuit driven driven driven thrm# core thermal sensor driven off off thrmtrip# cpu thermal sensor driven off off vrmpwrgd suspend processor voltage regulator high low low wake# suspend external pull-up driven driven driven processor interface a20gate core external microcontroller static off off ferr# core processor static off off rcin# core external microcontroller high off off table 3-3. power plane for input signal s for configurations (sheet 2 of 3) signal name power well driver during reset c3/c4 s1 s3 s4/s5 http://www..net/ datasheet pdf - http://www..net/ intel ? ich10 pin states 90 datasheet notes: 1. these signals can be configured as outputs in gpio mode.the state of the dprslpvr and dprstp# signals in c4 are high if deeper sleep is enabled or low if it is disabled. 2. consumer only: cl_vref0 is driven by an ex ternal circuit except on platforms where the mch does not support controller link. in these platforms, the signal is not driven. 3. corporate only: cl_vref0 may optionally be dr iven by an external ci rcuit, as configured by clinkvrefsel (ichstrp0:bit 5). smbus interface smbalert# / gpio11 / jtagtdo 1 (corporate only) suspend external pull-up driven driven driven system management interface intruder# rtc external switch driven high high miscellaneous signals intvrmen rtc external pull-up high high high lan100_slp rtc external pull-up high high high rtcrst# rtc external rc circuit high high high srtcrst# rtc external rc circuit high high high cl_vref0 controller link consumer only: external circuit 2 corporate only: internal circuit 3 driven driven driven tp0 / gpio72 (corporate only) suspend external pull-up high high high intel ? high definition audio interface hda_sdin[3:0] suspend intel high definition audio codec low low low spi interface spi_miso controller link internal pull-up driven driven driven intel ? quiet system technology tach[3:0]/ gpio[7,6,1,17] 1 core external pull-up driven off off clocks clk14 core clock generator running off off clk48 core clock generator running off off table 3-3. power plane for input signals for configurations (sheet 3 of 3) signal name power well driver during reset c3/c4 s1 s3 s4/s5 http://www..net/ datasheet pdf - http://www..net/ datasheet 91 intel ? ich10 and system clock domains 4 intel ? ich10 and system clock domains ta b l e 4 - 1 shows the system clock domains. figure 4-1 shows the assumed connection of the various system components, including the clock generator. for complete details of the system clocking solution, refer to the system?s clock generator component specification. table 4-1. intel ? ich10 and system clock domains clock domain frequency source usage ich10 sata_clkp, sata_clkn 100 mhz main clock generator differential clock pair used for sata. ich10 dmi_clkp, dmi_clkn 100 mhz main clock generator differential clock pair used for dmi. ich10 pciclk 33 mhz main clock generator free-running pci clock to intel ich10. this clock remains on during s0 and s1 state, and is expected to be shut off during s3 or below. system pci 33 mhz main clock generator pci bus, lpc i/f. these only go to external pci and lpc devices. ich10 clk48 48.000 mhz main clock generator super i/o, usb controllers. expected to be shut off during s3. ich10 clk14 14.31818 mhz main clock generator used for acpi timer and hpet timers. expected to be shut off during s3. glan_clk 5 to 62.5 mhz lan connect component generated by the lan connect component. expected to be shut off during s3. spi_clk 17.86 mhz/ 31.25 mhz ich generated by the ich. ex pected to be shut off during s3. http://www..net/ datasheet pdf - http://www..net/ intel ? ich10 and system clock domains 92 datasheet figure 4-1. ich10 conceptual system clock diagram intel ? ich10 32 khz xtal susclk# (32 khz) 14.31818 mhz stp_cpu# stp_pci# pci clocks (33 mhz) clock gen. 14.31818 mhz 48 mhz lan connect 100 mhz diff. pair 1 to 6 differential clock fan out device sata 100 mhz diff. pair dmi 100 mhz diff. pair pci express 100 mhz diff. pairs hd audio codec(s) 24 mhz 62.5 mhz 48.000 mhz 33 mhz http://www..net/ datasheet pdf - http://www..net/ datasheet 93 functional description 5 functional description this chapter describes the functions and interfaces of the intel ich10 family. 5.1 dmi-to-pci bridge (d30:f0) the dmi-to-pci bridge resides in pci device 30, function 0 on bus #0. this portion of the ich10 implements the buffering and co ntrol logic between pci and direct media interface (dmi). the arbitration for the pci bus is handled by this pci device. the pci decoder in this device must decode the rang es for the dmi. all register contents are lost when core well power is removed. direct media interface (dmi) is the chip-to-chip connection between the memory controller hub / graphics and memory cont roller hub ((g)mch) and i/o controller hub 10 (ich10). this high-speed interface integrates advanced priority-based servicing allowing for concurrent traffic and true isochronous transfer capabilities. base functionality is completely software transpar ent permitting current and legacy software to operate normally. to provide for true isochronous transfers and configurable quality of service (qos) transactions, the ich10 supports two virtual channels on dmi: vc0 and vc1. these two channels provide a fixed arbitration scheme where vc1 is always the highest priority. vc0 is the default conduit of traffic for dmi and is always enabled. vc1 must be specifically enabled and configured at both ends of the dmi link (i.e., the ich10 and (g)mch). configuration registers for dmi, virtual ch annel support, and dmi active state power management (aspm) are in the rcrb sp ace in the chipset config registers ( chapter 10 ). dmi is also capable of operating in an enterprise southbridge interface (esi) compatible mode. esi is a chip-to-chip co nnection for server chipsets. in this esi- compatible mode, the dmi signals require ac coupling. a hardware strap is used to configure dmi in esi-compatible mode see section 2.25 for details. 5.1.1 pci bus interface the ich10 pci interface supports pci local bus specification, revision 2.3 , at 33 mhz. the ich10 integrates a pci arbiter that support s up to four external pci bus masters in addition to the internal ich10 requests. 5.1.2 pci bridge as an initiator the bridge initiates cycles on the pci bus wh en granted by the pci arbiter. the bridge generates the cycle types listed in ta b l e 5 - 1 . table 5-1. pci bridge initiator cycle types command c/be# notes i/o read/write 2h/3h non-posted memory read/write 6h/7h writes are posted configuration read/write ah/bh non-posted special cycles 1h posted http://www..net/ datasheet pdf - http://www..net/ functional description 94 datasheet 5.1.2.1 memory reads and writes the bridge bursts memory writes on pci that are received as a single packet from dmi. 5.1.2.2 i/o reads and writes the bridge generates single dw i/o read and write cycles. when the cycle completes on the pci bus, the bridge generates a corresp onding completion on dmi. if the cycle is retried, the cycle is kept in the down bound queue and may be passed by a postable cycle. 5.1.2.3 configuration reads and writes the bridge generates single dw configuration read and write cycles. when the cycle completes on the pci bus, the bridge gene rates a corresponding completion. if the cycle is retried, the cycle is kept in th e down bound queue and may be passed by a postable cycle. 5.1.2.4 locked cycles the bridge propagates locks from dmi per the pci local bus specification . the pci bridge implements bus lock, which means the arbiter will not grant to any agent except dmi while locked. if a locked read results in a target or mast er abort, the lock is not established (as per the pci local bus specification ). agents north of the ich10 must not forward a subsequent locked read to the bridge if th ey see the first one finish with a failed completion. 5.1.2.5 target / master aborts when a cycle initiated by the bridge is ma ster/target aborted, the bridge will not re- attempt the same cycle. for multiple dw cycles, the bridge increments the address and attempts the next dw of the transaction. for all non-postable cycles, a target abort response packet is returned for each dw that was master or target aborted on pci. the bridge drops posted writes that abort. 5.1.2.6 secondary master latency timer the bridge implements a master latency timer via the smlt register which, upon expiration, causes the de-assertion of frame# at the next legal clock edge when there is another active request to use the pci bus. 5.1.2.7 dual address cycle (dac) the bridge will issue full 64-bit dual a ddress cycles for device memory-mapped registers above 4 gb. http://www..net/ datasheet pdf - http://www..net/ datasheet 95 functional description 5.1.2.8 memory and i/o decode to pci the pci bridge in the ich10 is a subtractive decode agent , which follows the following rules when forwarding a cycle from dmi to the pci interface: ? the pci bridge will positively decode any memory/io address within its window registers, assuming pcicmd.mse (d30:f0:offset 04h:bit 1) is set for memory windows and pcicmd.iose (d30:f0:offset 04h:bit 0) is set for io windows. ? the pci bridge will subtractively decode any 64-bit memo ry address not claimed by another agent, assuming pcicmd.mse (d30:f0:offset 04h:bit 1) is set. ? the pci bridge will subtractively decode any 16-bit i/o address not claimed by another agent assuming pcicmd.iose (d30:f0:offset 04h:bit 0) is set. ? if bctrl.ie (d30:f0:offset 3eh:bit 2) is set, the pci bridge will not positively forward from primary to secondary called out ranges in the io window per pci local bus specification (i/o transactions addressing the last 768 bytes in each, 1 kb block: offsets 100h to 3ffh). the pc i bridge will still take them subtractively assuming the above rules. ? if bctrl.vgae (d30:f0:offset 3eh:bit 3) is set, the pci bridge will positively forward from primary to secondary i/o and memory ranges as called out in the pci bridge specificatio n, assuming the above rules are met. 5.1.3 parity error detection and generation pci parity errors can be detected and repo rted. the following behavioral rules apply: ? when a parity error is detected on pci, the bridge sets the secsts.dpe (d30:f0:offset 1eh:bit 15). ? if the bridge is a master and bctrl.pere (d30:f0:offset 3eh:bit 0) is set and one of the parity errors defined below is detected on pci, then the bridge will set secsts.dpd (d30:f0:offset 1eh:bit 8) an d will also generate an internal serr#. ? during a write cycle, the perr# signal is active, or ? a data parity error is detected while performing a read cycle ? if an address or command parity error is detected on pci and pcicmd.see (d30:f0:offset 04h:bit 8), bctrl.pere, and bctrl.see (d30:f0:offset 3eh:bit 1) are all set, the bridge will set psts.sse (d30:f0:offset 06h:bit 14) and generate an internal serr#. ? if the psts.sse is set because of an ad dress parity error and the pcicmd.see is set, the bridge will generate an internal serr# ? when bad parity is detected from dmi, bad parity will be driven on all data from the bridge. ? when an address parity error is detected on pci, the pci bridge will never claim the cycle. this is a slight deviation from the pci bridge specification, which says that a cycle should be claimed if bctrl.pere is not set. howe ver, dmi does not have a concept of address parity error, so claiming the cycle could result in the rest of the system seeing a bad transaction as a good transaction. http://www..net/ datasheet pdf - http://www..net/ functional description 96 datasheet 5.1.4 pcirst# the pcirst# pin is genera ted under two conditions: ?pltrst# active ? bctrl.sbr (d30:f0:offset 3eh:bit 6) set to 1 the pcirst# pin is in the suspend well. pcir st# should be tied to pci bus agents, but not other agents in the system. 5.1.5 peer cycles the pci bridge may be the initiator of peer cycles. peer cycles include memory, io, and configuration cycle types. peer cycles are only allowed through vc0, and are enabled with the following bits: ? bpc.pde (d30:f0:offset 4ch:bit 2) ? memory and i/o cycles ? bpc.cde (d30:f0:offset 4ch:bit 1) ? configuration cycles when enabled for peer for one of the above cycle types, the pci bridge will perform a peer decode to see if a peer agent can receive the cycle. when not enabled, memory cycles (posted and/or non-posted) are sent to dmi, and i/o and/or configuration cycles are not claimed. configuration cycles have special considerations. under the pci local bus specification , these cycles are not allowed to be forwarded upstream through a bridge. however, to enable things such as manage ability, bpc.cde can be set. wh en set, type 1 cycles are allowed into the part. the address format of the type 1 cycle is slightly different from a standard pci configuration cycle to allow addr essing of extended pci space. the format is shown in ta b l e 5 - 2 . note: the ich10?s usb controllers cannot perform peer-to-peer traffic. 5.1.6 pci-to-pci bridge model from a software perspective, the ich10 contains a pci-to-pci bridge. this bridge connects dmi to the pci bus. by using the pci-to-pci bridge software model, the ich10 can have its decode ranges programmed by existing plug-and-play software such that pci ranges do not conflict with graphics aperture ranges in the host controller. table 5-2. type 1 address format bits definition 31:27 reserved (same as the pci local bus specification ) 26:24 extended configuration address ? allows addressing of up to 4k. these bits are combined with bits 7:2 to get the full register. 23:16 bus number (same as the pci local bus specification ) 15:11 device number (same as the pci local bus specification ) 10:8 function number (same as the pci local bus specification ) 7:2 register (same as the pci local bus specification ) 10 0 must be 1 to indicate a type 1 cycle. type 0 cycles are not decoded. http://www..net/ datasheet pdf - http://www..net/ datasheet 97 functional description 5.1.7 idsel to device number mapping when addressing devices on the external pci bus (with the pci slots), the ich10 asserts one address signal as an idsel. wh en accessing device 0, the ich10 asserts ad16. when accessing device 1, the ich10 asserts ad17. this mapping continues all the way up to device 15 where the ich10 asse rts ad31. note that the ich10?s internal functions (intel high definition audio, usb, sata and pci bridge) are enumerated like they are off of a separate pci bu s (dmi) from the external pci bus. 5.1.8 standard pci bus configuration mechanism the pci bus defines a slot based ?configuration space? that allows each device to contain up to eight functions with each function containing up to 256, 8-bit configuration registers. the pci local bus specification, revision 2.3 defines two bus cycles to access the pci configuration space: configuration read and configuration write. memory and i/o spaces are supported directly by the processor. configuration space is supported by a mapping mechan ism implemented within the ich10. the pci local bus specification, revision 2.3 defines two mechanisms to access configuration space, mechanism 1 and mechanism 2. the ich10 only supports mechanism 1. warning: configuration writes to internal devices, wh en the devices are disabled, are invalid and may cause undefined results. 5.2 pci express* root ports (d28:f0,f1,f2,f3,f4,f5) there are six root ports available in ich10. these all reside in device 28, and take function 0 ? 5. port 1 is function 0, port 2 is function 1, port 3 is function 2, port 4 is function 3, port 5 is function 4, and port 6 is function 5. pci express root ports 1-4 can be statically configured as four x1 ports or ganged together to form one x4 port. ports 5 and 6 ca n only be used as two x1 ports. the port configuration is set by rcba 224h [bits 1:0] see section 10.1.38 for more details. 5.2.1 interrupt generation the root port generates interrupts on behalf of hot-plug and power management events, when enabled. these interrupts can ei ther be pin based, or can be msis, when enabled. when an interrupt is generated via the legacy pin, the pin is internally routed to the ich10 interrupt controllers. the pin that is driven is based upon the setting of the chipset configuration registers. specifically, the chipset conf iguration registers used are the d28ip (base address + 310ch) and d28ir (base address + 3146h) registers. http://www..net/ datasheet pdf - http://www..net/ functional description 98 datasheet ta b l e 5 - 3 summarizes interrupt behavior for msi and wire-modes. in the table ?bits? refers to the hot-plug and pme interrupt bits. 5.2.2 power management 5.2.2.1 s3/s4/s5 support software initiates the transition to s3/s4/s5 by performing an io write to the power management control register in the ich10. after the io write completion has been returned to the processor, each root port will send a pme_turn_off tlp (transaction layer packet) message on its downstream link. the device attached to the link will eventually respond with a pme_to_ack tlp message followed by sending a pm_enter_l23 dllp (data link layer packet) request to enter the l2/l3 ready state. when all of the ich10 root ports links are in the l2/l3 ready state, the ich10 power management control logic will proceed with the entry into s3/s4/s5. prior to entering s3, software is re quired to put each device into d3 hot . when a device is put into d3 hot it will initiate entry into a l1 link state by sending a pm_enter_l1 dllp. thus under normal operating cond itions when the root ports sends the pme_turn_off message the link will be in st ate l1. however, when the root port is instructed to send the pme_turn_off message , it will send it whether or not the link was in l1. endpoints attached to ich can make no assumptions about the state of the link prior to receiving a pme_turn_off message. 5.2.2.2 resuming from suspended state the root port contains enough circuitry in the suspend well to detect a wake event through the wake# signal and to wake the system. when wake# is detected asserted, an internal signal is sent to the power management controller of the ich10 to cause the system to wake up. this internal message is not logged in any register, nor is an interrupt/gpe generated due to it. 5.2.2.3 device initia ted pm_pme message when the system has returned to a working state from a previous low power state, a device requesting service will send a pm_p me message continuously, until acknowledge by the root port. the root port will take di fferent actions depending upon whether this is the first pm_pme has been received, or whether a previous message has been received but not yet serviced by the operating system. table 5-3. msi versus pci irq actions interrupt register wire-mode action msi action all bits 0 wire inactive no action one or more bits set to 1 wire active send message one or more bits set to 1, new bit gets set to 1 wire active send message one or more bits set to 1, software clears some (but not all) bits wire active send message one or more bits set to 1, software clears all bits wire inactive no action software clears one or more bi ts, and one or more bits are set on the same clock wire active send message http://www..net/ datasheet pdf - http://www..net/ datasheet 99 functional description if this is the first message received (rsts.ps - d28:f0/f1/f2/f3/f4/f5:offset 60h:bit 16 is cleared), the root port will set rsts .ps, and log the pme requester id into rsts.rid (d28:f0/f1/f2/f3/f4/f5:offset 60h:bits 15:0). if an interrupt is enabled via rctl.pie (d28:f0/f1/f2/f3/f4/f5:offset 5ch: bit 3), an interrupt will be generated. this interrupt can be either a pin or an ms i if msi is enabled via mc.msie (d28:f0/f1/ f2/f3/f4/f5:offset 82h:bit 0). see section 5.2.2.4 for smi/sci generation. if this is a subsequent message received (rst s.ps is already set), the root port will set rsts.pp (d28:f0/f1/f2/f3/f4/f5:offset 60h:bit 17) and log the pme requester id from the message in a hidden register. no other action will be taken. when the first pme event is cleared by softwa re clearing rsts.ps, the root port will set rsts.ps, clear rsts.pp, and move the requester id from the hidden register into rsts.rid. if rctl.pie is set, an interrupt will be gene rated. if rctl.pie is not set, a message will be sent to the power management controller so that a gpe can be set. if messages have been logged (rsts.ps is set), and rctl.pie is later written from a 0 to a 1, and interrupt will be generated. this last co ndition handles the case where the message was received prior to the operating system re-enabling interrupts after resuming from a low power state. 5.2.2.4 smi/sci generation interrupts for power management events are not supported on legacy operating systems. to support power management on non-pci express aware operating systems, pm events can be routed to generate sci. to generate sci, mpc. pmce must be set. when set, a power management event will cause smscs.pmcs (d28:f0/f1/f2/f3/f4/ f5:offset dch:bit 31) to be set. additionally, bios workarounds for power management can be supported by setting mpc.pmme (d28:f0/f1/f2/f3/f4/f5:offset d8 h:bit 0). when this bit is set, power management events will set smscs.pmms (d28:f0/f1/f2/f3/f4/f5:offset dch:bit 0), and smi # will be generated. this bit will be set regardless of whether interrupts or sci is enabled. the smi# may occur conc urrently with an interrupt or sci. 5.2.3 serr# generation serr# may be generated via two paths ? thro ugh pci mechanisms involving bits in the pci header, or through pci express * mechanisms involving bits in the pci express capability structure. figure 5-1. generation of serr# to platform psts.sse serr# pcicmd.see secondary parity error primary parity error secondary serr# correctable serr# fatal serr# non-fatal serr# pci pci express http://www..net/ datasheet pdf - http://www..net/ functional description 100 datasheet 5.2.4 hot-plug each root port implements a hot-plug controller which performs the following: ? messages to turn on / off / blink leds ? presence and attention button detection ? interrupt generation the root port only allows hot-plug with modules (e.g., expresscard*). edge-connector based hot-plug is not supported. 5.2.4.1 presence detection when a module is plugged in and power is supplied, the physical layer will detect the presence of the device, and the root po rt sets slsts.pds (d28:f0/f1/f2/f3/f4/ f5:offset 5ah:bit 6) and slsts.pdc (d28:f0/f1/f2/f3:offset 6h:bit 3). if slctl.pde (d28:f0/f1/f2/f3f4/f5:offset 58h:bit 3) and slctl.hpe (d28:f0/f1/f2/f3f4/ f5:offset 58h:bit 5) are both set, the root port will also generate an interrupt. when a module is removed (via the physical layer detection), the root port clears slsts.pds and sets slsts.pdc. if slctl.pde and slctl.hpe are both set, the root port will also generate an interrupt. 5.2.4.2 message generation when system software writes to slctl.aic (d28:f0/f1/f2/f3f4/f5:offset 58h:bits 7:6) or slctl.pic (d28:f0/f1/f2/f3f4/f5:offset 58h:bits 9:8), the root port will send a message down the link to change the state of leds on the module. writes to these fields are non-postable cycles, and the resulting message is a postable cycle. when receiving one of these writes , the root port performs the following: ? changes the state in the register. ? generates a completion into the upstream queue ? formulates a message for the downstream port if the field is written to regardless of if the field changed. ? generates the message on the downstream port ? when the last message of a command is transmitted, sets slsts.cce (d28:f0/f1/ f2/f3f4/f5:offset 58h:bit 4) to indi cate the command has completed. if slctl.cce and slctl.hpe (d28:f0/f1/f2/f3f4/f5:offset 58h:bit 5) are set, the root port generates an interrupt. the command completed register (slsts.cc) applies only to commands issued by software to control the attention indicator (slctl.aic), power in dicator (slctl.pic), or power controller (slctl.pcc). however, wr ites to other parts of the slot control register would invariably end up writing to the indicators, power controller fields; hence, any write to the slot control register is considered a command and if enabled, will result in a command complete interrupt. the only exception to this rule is a write to disable the command complete interrupt whic h will not result in a command complete interrupt. a single write to the slot control register is considered to be a single command, and hence receives a single command complete, even if the write affects more than one field in the slot control register. http://www..net/ datasheet pdf - http://www..net/ datasheet 101 functional description 5.2.4.3 attention button detection when an attached device is ejected, an a ttention button could be pressed by the user. this attention button press will result in a the pci express message ?attention_button_pressed? from the device . upon receiving this message, the root port will set slsts.abp (d28:f0/f1/f2/f3f4/f5:offset 5ah:bit 0). if slctl.abe (d28:f0/f1/f2/f3f4/f5:offset 58h:bit 0) and slctl.hpe (d28:f0/f1/f2/ f3f4/f5:offset 58h:bit 5) are set, the hot-plug controller will also generate an interrupt. the interrupt is generated on an edge-event. for example, if slsts.abp is already set, a new interrupt will not be generated. 5.2.4.4 smi/sci generation interrupts for hot-plug events are not supp orted on legacy operating systems. to support hot-plug on non-pci express aware operating systems, hot-plug events can be routed to generate sci. to generate sc i, mpc.hpce (d28:f0/f1/f2/f3f4/f5:offset d8h:bit 30) must be set. when set, enab led hot-plug events will cause smscs.hpcs (d28:f0/f1/f2/f3f4/f5:offset dch:bit 30) to be set. additionally, bios workarounds for hot-plug can be supported by setting mpc.hpme (d28:f0/f1/f2/f3f4/f5:offset d8h:bit 1). when this bit is set, hot-plug events can cause smi status bits in smscs to be se t. supported hot-plug events and their corresponding smscs bit are: ? command completed - scscs.hpccm (d28:f0/f1/f2/f3/f4/f5:offset dch:bit 3) ? presence detect changed - smscs.hppdm (d28:f0/f1/f2/f3/f4/f5:offset dch:bit 1) ? attention button pressed - smscs.hpabm (d28:f0/f1/f2/f3/f4/f5:offset dch:bit 2) ? link active state changed - smscs.hplas (d28:f0/f1/f2/f3/f4/f5:offset dch:bit 4) when any of these bits are set, smi # will be generated. these bits are set regardless of whether interrupts or sci is enabled for hot-plug events. the smi# may occur concurrently with an interrupt or sci. 5.3 gigabit ethernet controller (b0:d25:f0) the ich10 integrates a gigabit ethernet controller. the integrated gigabit ethernet controller is compatible with gigabit ethernet phy (intel ? 82567 gigabit platform lan connect device). the integrated gigabit ethernet controller provides two interfaces: lan connect interface (lci) for 10/100 operation and gigabit lan connect interface (glci) for gigabit ethernet operation. the glci is shared with the ich10?s pci express port 6 and can be enabled via a soft strap that is stored in system spi flash, see section for details. the ich10 integrated gigabit ethernet co ntroller supports multi speed operation, 10/100/1000 mb/s. the integrated gigabit ethe rnet can operate in full-duplex at all supported speeds or half-duplex at 10/100 mb/s, and adheres with the ieee 802.3x flow control specification. note: gigabit ethernet (1000mb/s) is only supported in s0. the controller provides a system interface via a pci function. a full memory-mapped or io-mapped interface is provided to the soft ware, along with dma mechanisms for high performance data transfer. http://www..net/ datasheet pdf - http://www..net/ functional description 102 datasheet the following summarizes the ich10 integrat ed gigabit ethernet controller features: ? configurable led operation for customization of led display. ? ipv4 and ipv6 checksum offload support (receive, transmit, and large send). ? 64-bit address master support for system using more than 4 gb of physical memory. ? configurable receive and transmit data fifo, programmable in 1 kb increments. ? intelligent interrupt generation to enhance driver performance. ? compliance with advanced configuration and power interface and pci power management standards. ? acpi register set and power down functi onality supporting d0 and d3 states. ? full wake-up support (apm and acpi). ? magic packet wake-up enable with unique mac address. ? fragmented udp checksum off load for package reassembly. ? jumbo frames supported. ? linksec support (802.3ae compliant) ? timesync support (802.1as compliant) 5.3.1 gigabit ethernet pci bus interface the gigabit ethernet controller has a pci interface to the host processor and host memory. the following sections detail the transaction on the bus. 5.3.1.1 transaction layer the upper layer of the host architecture is the transaction layer. the transaction layer connects to the device core using an implem entation specific protocol. through this core-to-transaction-layer protocol, the applicat ion-specific parts of the device interact with the subsystem and transmit and receive requests to or from the remote agent, respectively. 5.3.1.2 data alignment 5.3.1.2.1 4 k boundary pci requests must never specify an address/ length combination that causes a memory space access to cross a 4 k boundary. it is the hw responsibility to break requests into 4 k-aligned requests (if needed). this does not pose any requirement on sw. however, if sw allocates a buffer across a 4 k boundary, hw will issue multiple requests for the buffer. sw should consider aligning buffers to 4 kb boundary in cases where it improves performance. the alignment to the 4 k boundaries is done in the core. the transaction layer will not do any alignment according to these boundaries. 5.3.1.2.2 64 bytes pci requests are multiples of 64 bytes an d aligned to make better use of memory controller resources. writes, however, can be on any boundary and can cross a 64 byte alignment boundary 5.3.1.3 configuration request retry status the lan controller might have a delay in initialization due to nvm read. if the nvm configuration read operation is not complete d and the device receives a configuration request, the device will resp ond with a configuration request retry completion status to terminate the request, and thus effectiv ely stall the configuration request until such time that the subsystem has completed local initialization and is ready to communicate with the host. http://www..net/ datasheet pdf - http://www..net/ datasheet 103 functional description 5.3.2 error events and error reporting 5.3.2.1 data parity error the pci host bus does not provide parity prot ection, but it does forward parity errors from bridges. the lan controller recognizes parity errors through the internal bus interface and will set the parity error bit in pc i configuration space. if parity errors are enabled in configuration space, a system erro r will be indicated on the pci host bus to the chipset. the offending cycle with a pari ty error will be dropped and not processed by the lan controller. 5.3.2.2 completion with unsu ccessful completion status a completion with unsuccessful completion st atus (any status other than "000") will be dropped and not processed by the lan cont roller. furthermore, the request that corresponds to the unsuccessful completion will not be retried. when this unsuccessful completion status is received, the system error bit in the pci configuration space will be set. if the system errors are enabled in configuration space, a system error will be indicated on the pci host bus to the chipset. 5.3.3 ethernet interface the integrated lan controller provides a co mplete csma/cd function supporting ieee 802.3 (10mb/s), 802.3u (100mb/s) implementa tions. it also supports the ieee 802.3z and 802.3ab (1000mb/s) implementations. th e device performs all of the functions required for transmission, reception and co llision handling called out in the standards. the mode used to communicate between the lan controller and the lan connect device supports 10/100/1000 mbps operation, with both half- and full-duplex operation at 10/100 mbps, and full-duplex operation at 1000 mbps. 5.3.3.1 mac/lan connect interface the integrated lan controller and lan connect device communicate through either the platform lan connect interface (lci) or gigabit lan connect interface (glci). all controller configuration is performed using device control registers mapped into system memory or i/o space. the lan connect device is configured via the lci or gigabit ethernet lan connect interface. the integrated mac supports various modes as summarized in the following table table 5-4. lan mode support mode interface active connections normal 10/100/1000 lci, glci intel ? 82567 gigabit platform lan connect device http://www..net/ datasheet pdf - http://www..net/ functional description 104 datasheet 5.3.4 pci power management the lan controller supports the advanced configuration and power interface (acpi) specification as well as advanced power manage ment (apm). this allows the host to be awoken (i.e., from sx (s3-s5) to s0) by network-related activity via an internal host wake signal. the lan controller contains power management registers for pci, and supports d0 and d3 states. pci transactions are only allowed in the d0 state, except for host accesses to the lan controller?s pci configuration registers. 5.3.4.1 wake-up the lan controller supports two types of wakeup mechanisms: 1. advanced power management (apm) wakeup 2. acpi power management wakeup both mechanisms use an internal wake# signal to wake the system up. this signal is connected to the suspend wake logic in th e ich10. the wake-up steps are as follows: 1. host wake event occurs (note that packet is not delivered to host) 2. pme_status bit is set 3. internal wake# signal asserted by host lan function 4. system wakes from sx state to s0 state 5. the host lan function is transitioned to d0 6. the host clears the pme_status bit 7. internal wake# signal is deasserted by host lan function 5.3.4.1.1 advanced power management wakeup advanced power management wakeup, or apm wakeup, was previously known as wake on lan. it is a feature that has existed in the 10/100 mbps nics for several generations. the basic premise is to receive a broadcast or unicast packet with an explicit data pattern, and then to assert a signal to wake-up the system. in the earlier generations, this was accomplished by using a special signal that ran across a cable to a defined connector on the motherboard. the nic would assert the signal for approximately 50ms to signal a wakeup. the lan controller uses (if configured to) an in-band pm_pme message for this. on power-up, the lan controller will read the apm enable bits from the nvm pci init control word into the apm enable (apme) bi ts of the wakeup control register (wuc). these bits control enabling of apm wakeup. when apm wakeup is enabled, the lan contro ller checks all incoming packets for magic packets. once the lan controller receives a matching magic packet, it will: ? set the magic packet received bit in the wake up status register (wus). ? set the pme_status bit in the power management control / status register (pmcsr) and assert the internal wake# signal. apm wakeup is supported in all power states and only disabled if a subsequent nvm read results in the apm wake up bit being cl eared or the software explicitly writes a 0 to the apm wake up (apm) bit of the wuc register. http://www..net/ datasheet pdf - http://www..net/ datasheet 105 functional description 5.3.4.1.2 acpi power management wakeup the lan controller supports acpi power management based wakeups. it can generate system wake-up events from three sources: ? reception of a magic packet. ? reception of a network wakeup packet. ? detection of a link change of state. activating acpi power management wakeup requires the following steps: ? the driver programs the wake up filter control register (wufc) to indicate the packets it wishes to wake up from and supplies the necessary data to the ipv4 address table (ip4at) and the flexible filter mask table (ffmt), flexible filter length table (fflt), and the flexible filter value table (ffvt). it can also set the link status change wake up enable (lnkc) bit in the wake up filter control register (wufc) to cause wakeup when the link changes state. ? the os (at configuration time) writes a 1 to the pme_en bit of the power management control / status register (pmcsr.8). normally, after enabling wakeup, the os will write 11b to the lower two bits of the pmcsr to put the lan controller into low-power mode. once wakeup is enabled, the lan controller monitors incoming packets, first filtering them according to its standard address filter ing method, then filtering them with all of the enabled wakeup filters. if a packet pa sses both the standard address filtering and at least one of the enabled wakeup filters, the lan controller will: ? set the pme_status bit in the power management control / status register (pmcsr) ? if the pme_en bit in the power management control / status register (pmcsr) is set, assert the internal wake# signal. ? set one or more of the received bits in the wake up status register (wus). (more than one bit will be set if a packet matches more than one filter.) if enabled, a link state change wakeup will cause similar results, setting pme_status, asserting the internal wake# signal and setti ng the link status changed (lnkc) bit in the wake up status register (wus) when the link goes up or down. the internal wake# signal will remain assert ed until the os either writes a 1 to the pme_status bit of the pmcsr register or writes a 0 to the pme_en bit. after receiving a wakeup packet, the lan co ntroller will ignore any subsequent wakeup packets until the driver clears all of the received bits in the wake up status register (wus). it will also ignore link change events until the driver clears the link status changed (lnkc) bit in the wake up status register (wus). 5.3.5 configurable leds the lan controller supports 3 controllable an d configurable leds that are driven from the lan connect device. each of the three le d outputs can be individually configured to select the particular event, state, or acti vity, which will be indicated on that output. in addition, each led can be individually configured for output polarity as well as for blinking versus non-blinking (steady-state) indication. the configuration for led outputs is specifie d via the ledctl register. furthermore, the hardware-default configuration for all the le d outputs, can be spec ified via nvm fields, thereby supporting led displays configur able to a particular oem preference. http://www..net/ datasheet pdf - http://www..net/ functional description 106 datasheet each of the 3 led's may be configured to use one of a variety of sources for output indication. the mode bits control the led source: ? link_100/1000 is asserted when link is established at either 100 or 1000mbps. ? link_10/1000 is asserted when link is established at either 10 or 1000mbps. ? link_up is asserted when any spee d link is established and maintained. activity is asserted when link is established and packets are being transmitted or received. ? link/activity is asserted when link is established and there is no transmit or receive activity ? link_10 is asserted when a 10mbps link is established and maintained. ? link_100 is asserted when a 100mbps link is established and maintained. ? link_1000 is asserted when a 1000mbps link is established and maintained. ? full_duplex is asserted when the link is configured for full duplex operation. ? collision is asserted when a collision is observed. ? paused is asserted when the device's transmitter is flow controlled. ? led_on is always asserted; led_off is always de-asserted. the ivrt bits allow the led source to be inverted before being output or observed by the blink-control logic. led outputs are a ssumed to normally be connected to the negative side (cathode) of an external led. the blink bits control whether the led shou ld be blinked while the led source is asserted, and the blinking frequency (either 200 ms on and 200 ms off or 83 ms on and 83 ms off). the blink control may be espe cially useful for ensuring that certain events, such as activity indication, cause led transitions, which are sufficiently visible to a human eye. the same blin king rate is shared by all leds. 5.3.6 function level reset support (flr) the gigabit lan controller supports the func tion level reset (flr) capability. the flr capability can be used in conjunction with intel virtualization technology. flr allows an operating system in a virtual machine to have complete control over a device, including its initialization, without interferin g with the rest of the platform. the device provides a software interface that enables the operating system to reset the whole device as if a pci reset was asserted. 5.3.6.1 flr steps 5.3.6.1.1 flr initialization 1. a flr is initiated by software writing a 1 to the initiate flr bit. 2. all subsequent requests targeting the function will not be claimed and will be master abort immediate on the bus. this includes any configuration, i/o or memory cycles, however, the function shall continue to accept completions targeting the function. 5.3.6.1.2 flr operation function will reset all configuration, i/o an d memory registers of the function except those indicated otherwise and reset all internal states of the function to the default or initial condition. http://www..net/ datasheet pdf - http://www..net/ datasheet 107 functional description 5.3.6.1.3 flr completion the initiate flr bit is reset (cleared) when the flr reset is completed. this bit can be used to indicate to the software that the flr reset is completed. note: from the time initiate flr bit is written to 1 software must wait at least 100 ms before accessing the function. 5.4 lpc bridge (w/ system and management functions) (d31:f0) the lpc bridge function of the ich10 resides in pci device 31:function 0. in addition to the lpc bridge function, d31:f0 contai ns other functional units including dma, interrupt controllers, timers, power mana gement, system management, gpio, and rtc. in this chapter, registers and functions associated with other functional units (power management, gpio, usb, etc.) are described in their respective sections. note: the lpc bridge cannot be configured as a subtractive decode agent. 5.4.1 lpc interface the ich10 implements an lpc interface as described in the low pin count interface specification, revision 1.1. the lpc interface to the ich10 is shown in figure 5-2 . note that the ich10 implements all of the signals that are shown as optional, but peripherals are not required to do so. figure 5-2. lpc interface diagram intel ? ich10 lpc device pci bus pci clk pci rst# pci serirq pci pme# lad [3:0] lframe# lpcpd# (optional) sus_stat# ldrq[1:0]# (optional) lsmi# (optional) gpi http://www..net/ datasheet pdf - http://www..net/ functional description 108 datasheet 5.4.1.1 lpc cycle types the ich10 (corporate only) implements a ll of the cycle types described in the low pin count interface specification, revision 1.1. ich10 consumer does not provide a generic mechanism for decoding memory rang es and forwarding them as standard lpc memory cycles on the lpc bus. ta b l e 5 - 5 shows the cycle types supported by the ich10. notes: 1. ich10 (corporate only) provides a single generic memory range (lgmr) for decoding memory cycles and forwarding them as lpc memo ry cycles on the lpc bus. the lgmr memory decode range is 64 kb in size and ca n be defined as being anywhere in the 4 gb memory space. this range needs to be config ured by bios during post to provide the necessary memory resources. bios should advertise the lpc generic memory range as reserved to the os in order to avoid resour ce conflict. for larger transfers, the ich10 performs multiple 8-bit transfers. if the cy cle is not claimed by any peripheral, it is subsequently aborted, and the ich10 returns a value of all 1s to the processor. this is done to maintain compatibility with isa memo ry cycles where pull-up resistors would keep the bus high if no device responds. 2. bus master read or write cycles must be naturally aligned. for example, a 1-byte transfer can be to any address. however, the 2-byte transfer must be word-aligned (i.e., with an address where a0=0). a dword transfer must be dword-aligned (i.e ., with an address where a1 and a0 are both 0). 5.4.1.2 start field definition note: all other encodings are reserved. table 5-5. lpc cycle types supported cycle type comment memory read (corporate only) 1 byte only. (see note 1 below) memory write (corporate only) 1 byte only. (see note 1 below) i/o read 1 byte only. intel ich10 breaks up 16- and 32-bit processor cycles into multiple 8-bit transfers. i/o write 1 byte only. ich10 breaks up 16- and 32-bit processor cycles into multiple 8-bit transfers. dma read can be 1, or 2 bytes dma write can be 1, or 2 bytes bus master read can be 1, 2, or 4 bytes. (see note 2 below) bus master write can be 1, 2, or 4 bytes. (see note 2 below) table 5-6. start field bit definitions bits[3:0] encoding definition 0000 start of cycle for a generic target 0010 grant for bus master 0 0011 grant for bus master 1 1111 stop/abort: end of a cycle for a target. http://www..net/ datasheet pdf - http://www..net/ datasheet 109 functional description 5.4.1.3 cycle type / direction (cyctype + dir) the ich10 always drives bit 0 of this field to 0. peripherals running bus master cycles must also drive bit 0 to 0. ta b l e 5 - 7 shows the valid bit encodings. 5.4.1.4 size bits[3:2] are reserved. the ich10 always drives them to 00. peripherals running bus master cycles are also supposed to drive 00 for bits 3:2; however, the ich10 ignores those bits. bits[1:0] are encoded as listed in ta b l e 5 - 8 . table 5-7. cycle type bit definitions bits[3:2] bit1 definition 00 0 i/o read 00 1 i/o write 01 0 memory read 01 1 memory read 10 0 dma read 10 1 dma write 11 x reserved. if a peripheral performing a bus master cycle generates this value, the intel ich10 aborts the cycle. table 5-8. transfer size bit definition bits[1:0] size 00 8-bit transfer (1 byte) 01 16-bit transfer (2 bytes) 10 reserved. the intel ich10 never drives this combination. if a peripheral running a bus master cycle drives this combination, the ich10 may abort the transfer. 11 32-bit transfer (4 bytes) http://www..net/ datasheet pdf - http://www..net/ functional description 110 datasheet 5.4.1.5 sync valid values for the sync field are shown in ta b l e 5 - 9 . notes: 1. all other combinations are reserved. 2. if the lpc controller receives any sync retu rned from the device ot her than short (0101), long wait (0110), or ready (0000) when runn ing a fwh cycle, indeterminate results may occur. a fwh device is not allo wed to assert an error sync. 5.4.1.6 sync time-out there are several error cases that can occur on the lpc interface. the ich10 responds as defined in section 4.2.1.9 of the low pin count interface specification , revision 1.1 to the stimuli described therein. there ma y be other peripheral failure conditions; however, these are not handled by the ich10. 5.4.1.7 sync error indication the ich10 responds as defined in section 4.2.1.10 of the low pin count interface specification, revision 1.1. upon recognizing the sync field indicating an error, the ich10 treats this as an serr by reporting this into the device 31 error reporting logic. table 5-9. sync bit definition bits[3:0] indication 0000 ready: sync achieved with no error. for dma transfers, this also indicates dma request deassertion and no more transfers desired for that channel. 0101 short wait: part indicating wait-states. for bus master cycles, the intel ? ich10 does not use this encoding. instead, the ich10 uses the long wait encoding (see next encoding below). 0110 long wait: part indicating wait-states, and ma ny wait-states will be added. this encoding driven by the ich10 for bus master cycles, rather than the short wait (0101). 1001 ready more (used only by peripheral for dma cycle): sync achieved with no error and more dma transfers desired to continue after this transfer. this value is valid only on dma transfers and is not allowed for any other type of cycle. 1010 error: sync achieved with error. this is generally used to replace the serr# or iochk# signal on the pci/isa bus. it indica tes that the data is to be transferred, but there is a serious error in this tran sfer. for dma transfers, this not only indicates an error, but also indicate s dma request deasse rtion and no more transfers desired for that channel. http://www..net/ datasheet pdf - http://www..net/ datasheet 111 functional description 5.4.1.8 lframe# usage the ich10 follows the usage of lframe# as defined in the low pin count interface specification, revision 1.1. the ich10 performs an abort for the following cases (possible failure cases): ? ich10 starts a memory, i/o, or dma cycle, but no device drives a valid sync after four consecutive clocks. ? ich10 starts a memory, i/o, or dma cycle, and the peripheral drives an invalid sync pattern. ? a peripheral drives an invalid address when performing bus master cycles. ? a peripheral drives an invalid value. 5.4.1.9 i/o cycles for i/o cycles targeting registers specified in the ich10?s decode ranges, the ich10 performs i/o cycles as defined in the low pin count interface specification, revision 1.1. these are 8-bit transfers. if the processor attempts a 16-bit or 32-bit transfer, the ich10 breaks the cycle up into multiple 8-bit transfers to consecutive i/o addresses. note: if the cycle is not claimed by any peripher al (and subsequently aborted), the ich10 returns a value of all 1s (ffh) to the processor. this is to maintain compatibility with isa i/o cycles where pull-up resistors would keep the bus high if no device responds. 5.4.1.10 bus master cycles the ich10 supports bus master cycles and re quests (using ldrq#) as defined in the low pin count interface specification, revision 1.1. the ich10 has two ldrq# inputs, and thus supports two separate bus master devices. it uses the associated start fields for bus master 0 (0010b) or bus master 1 (0011b). note: the ich10 does not support lpc bus masters performing i/o cycles. lpc bus masters should only perform memory read or memory write cycles. 5.4.1.11 lpc power management lpcpd# protocol same timings as for sus_stat#. upon driving sus_stat# low, lpc peripherals drive ldrq# low or tri-state it. ich10 shuts of f the ldrq# input buffers. after driving sus_stat# active, the ich10 drives lframe# low, and tri-states (or drive low) lad[3:0]. note: the low pin count interface specification, revision 1.1 defines the lpcpd# protocol where there is at least 30 s from lpcpd# assertion to lrst# assertion. this specification explicitly states that this prot ocol only applies to entry/exit of low power states which does not include asynchrono us reset events. the ich10 asserts both sus_stat# (connects to lpcpd#) and pltrst# (connects to lrst#) at the same time when the core logic is reset (via cf9h, pw rok, or sys_reset#, etc.). this is not inconsistent with the lpc lpcpd# protocol. http://www..net/ datasheet pdf - http://www..net/ functional description 112 datasheet 5.4.1.12 configuration and intel ? ich10 implications lpc i/f decoders to allow the i/o cycles and memory mapped cycles to go to the lpc interface, the ich10 includes several decoders. during configuration, the ich10 must be programmed with the same decode ranges as the peripheral. the decoders are programmed via the device 31:function 0 configuration space. note: the ich10 cannot accept pci write cycles from pci-to-pci bridges or devices with similar characteristics (specifically those with a ?retry read? feature which is enabled) to an lpc device if there is an outstandin g lpc read cycle towards the same pci device or bridge. these cycles are not part of normal system operation, but may be encountered as part of platform validat ion testing using custom test fixtures. bus master device mapping and start fields bus masters must have a unique start field. in the case of the ich10 that supports two lpc bus masters, it drives 0010 for the start field for grants to bus master #0 (requested via ldrq0#) and 0011 for grants to bus master #1 (requested via ldrq1#.). thus, no registers are needed to configure the start fields for a particular bus master. 5.5 dma operation (d31:f0) the ich10 supports lpc dma using the ich 10?s dma controller. the dma controller has registers that are fixed in the lower 64 kb of i/o space. the dma controller is configured using registers in the pci co nfiguration space. these registers allow configuration of the channels for use by lpc dma. the dma circuitry incorporates the functionality of two 82c37 dma controllers with seven independently programmable channels ( figure 5-3 ). dma controller 1 (dma-1) corresponds to dma channels 0?3 and dm a controller 2 (dma-2) corresponds to channels 5?7. dma channel 4 is used to cascade the two controllers and defaults to cascade mode in the dma channel mode (dcm) register. channel 4 is not available for any other purpose. in addition to acce pting requests from dma slaves, the dma controller also responds to requests that software initiates. software may initiate a dma service request by setting any bit in the dma channel request register to a 1. each dma channel is hardwired to the co mpatible settings for dma device size: channels [3:0] are hardwired to 8-bit, count-by-bytes transfers, and channels [7:5] are hardwired to 16-bit, count-by-words (address shifted) transfers. ich10 provides 24-bit addressing in complia nce with the isa-compatible specification. each channel includes a 16-bit isa-compatible current register which holds the 16 least-significant bits of the 24-bit address, an isa-compatible page register which contains the eight next most significant bits of address. the dma controller also features refresh ad dress generation, and auto-initialization following a dma termination. figure 5-3. intel ? ich10 dma controller channel 0 channel 1 channel 2 channel 3 channel 4 channel 5 channel 6 channel 7 dma-1 dma-2 http://www..net/ datasheet pdf - http://www..net/ datasheet 113 functional description 5.5.1 channel priority for priority resolution, the dma consists of two logical channel groups: channels 0?3 and channels 4?7. each group may be in either fixed or rotate mode, as determined by the dma command register. dma i/o slaves normally assert their dreq line to arbitrate for dma service. however, a software request for dma service can be presented through each channel's dma request register. a software request is subject to the same prioritization as any hardware request. see the detailed register description for request register programming information in section 13.2 . 5.5.1.1 fixed priority the initial fixed priority structure is as follows: the fixed priority ordering is 0, 1, 2, 3, 5, 6, and 7. in this scheme, channel 0 has the highest priority, and channel 7 has the lowest priority. channels [3:0] of dma-1 assume the priority position of channel 4 in dma-2, t hus taking priority over channels 5, 6, and 7. 5.5.1.2 rotating priority rotation allows for ?fairness? in priority resolution. the priority chain rotates so that the last channel serviced is assigned the lowest priority in the channel group (0?3, 5?7). channels 0?3 rotate as a group of 4. they are always placed between channel 5 and channel 7 in the priority list. channel 5?7 rotate as part of a group of 4. that is, channels (5?7) form the first three positions in the rotation, while channel group (0?3) comprises the fourth position in the arbitration. 5.5.2 address compatibility mode when the dma is operating, the addresses do not increment or decrement through the high and low page registers. therefore, if a 24-bit address is 01ffffh and increments, the next address is 010000h, not 020000h. similarly, if a 24-bit address is 020000h and decrements, the next address is 02ffffh , not 01ffffh. however, when the dma is operating in 16-bit mode, the addresses still do not increment or decrement through the high and low page registers but the page boundary is now 128 k. therefore, if a 24-bit address is 01fffeh and increments, the next address is 000000h, not 0100000h. similarly, if a 24-bit address is 020000h and decrements, the next address is 03fffeh, not 02fffeh. this is compatible with the 82c37 and page register implementation used in the pc-at. this mode is set after cpurst is valid. high priority low priority 0, 1, 2, 3 5, 6, 7 http://www..net/ datasheet pdf - http://www..net/ functional description 114 datasheet 5.5.3 summary of dma transfer sizes ta b l e 5 - 1 0 lists each of the dma device transfer sizes. the column labeled ?current byte/word count register? indicates that the register contents represents either the number of bytes to transfer or the number of 16-bit words to transfer. the column labeled ?current address increment/decrem ent? indicates the number added to or taken from the current address register after each dma transfer cycle. the dma channel mode register determines if the cu rrent address register will be incremented or decremented. 5.5.3.1 address shifting when programmed for 16-b it i/o count by words the ich10 maintains compatibility with the implementation of the dma in the pc at that used the 82c37. the dma shifts the addresses for transfers to/from a 16-bit device count-by-words. note: the least significant bit of the low page re gister is dropped in 16-bit shifted mode. when programming the current address regi ster (when the dma channel is in this mode), the current address must be progra mmed to an even address with the address value shifted right by one bit. the address shifting is shown in ta b l e 5 - 1 1 . note: the least significant bit of the page regi ster is dropped in 16-bit shifted mode. 5.5.4 autoinitialize by programming a bit in the dma channel mode register, a channel may be set up as an autoinitialize channel. when a channel undergoes autoinitialization, the original values of the current page, current address and current byte/word count registers are automatically restored from the ba se page, address, and byte/word count registers of that channel following tc. the base registers are loaded simultaneously with the current registers by the mi croprocessor when the dma channel is programmed and remain unchanged throughout the dma service. the mask bit is not set when the channel is in autoinitialize. follo wing autoinitialize, the channel is ready to perform another dma service, without processo r intervention, as soon as a valid dreq is detected. table 5-10. dma transfer size dma device date size and word count current byte/word count register current address increment/ decrement 8-bit i/o, count by bytes bytes 1 16-bit i/o, count by words (address shifted) words 1 table 5-11. address shifting in 16-bit i/o dma transfers output address 8-bit i/o programmed address (ch 0?3) 16-bit i/o programmed address (ch 5?7) (shifted) a0 a[16:1] a[23:17] a0 a[16:1] a[23:17] 0 a[15:0] a[23:17] http://www..net/ datasheet pdf - http://www..net/ datasheet 115 functional description 5.5.5 software commands there are three additional special software commands that the dma controller can execute. the three software commands are: ? clear byte pointer flip-flop ?master clear ? clear mask register they do not depend on any specific bit pattern on the data bus. 5.6 lpc dma dma on lpc is handled through the use of the ldrq# lines from peripherals and special encodings on lad[3:0] from the ho st. single, demand, verify, and increment modes are supported on the lpc interface. channels 0?3 are 8 bit channels. channels 5?7 are 16-bit channels. channel 4 is reserved as a generic bus master request. 5.6.1 asserting dma requests peripherals that need dma service encode their requested channel number on the ldrq# signal. to simplify the protocol, each peripheral on the lpc i/f has its own dedicated ldrq# signal (they may not be shared between two separate peripherals). the ich10 has two ldrq# inputs, allowing at least two devices to support dma or bus mastering. ldrq# is synchronous with lclk (pci clock). as shown in figure 5-4 , the peripheral uses the following serial encoding sequence: ? peripheral starts the sequence by asserting ldrq# low (start bit). ldrq# is high during idle conditions. ? the next three bits contain the en coded dma channel number (msb first). ? the next bit (act) indicates whether the request for the indicated dma channel is active or inactive. the act bit is 1 (high) to indicate if it is active and 0 (low) if it is inactive. the case where act is low is rare , and is only used to indicate that a previous request for that channel is being abandoned. ? after the active/inactive indication, the ldrq# signal must go high for at least 1 clock. after that one clock, ldrq# signal can be brought low to the next encoding sequence. if another dma channel also needs to request a transfer, another sequence can be sent on ldrq#. for example, if an encoded request is sent for channel 2, and then channel 3 needs a transfer before the cycle for channe l 2 is run on the interface, the peripheral can send the encoded request for channel 3. th is allows multiple dma agents behind an i/o device to request use of th e lpc interface, and the i/o device does not need to self- arbitrate before sending the message. figure 5-4. dma request assertion through ldrq# start msb lsb act start lclk ldrq# http://www..net/ datasheet pdf - http://www..net/ functional description 116 datasheet 5.6.2 abandoning dma requests dma requests can be deasserted in two fash ions: on error conditions by sending an ldrq# message with the ?act? bit set to 0, or normally through a sync field during the dma transfer. this section describes boundary conditions where the dma request needs to be removed prior to a data transfer. there may be some special cases where the peripheral desires to abandon a dma transfer. the most likely case of this occurring is due to a floppy disk controller which has overrun or underrun its fifo, or so ftware stopping a device prematurely. in these cases, the peripheral wishes to stop further dma activity. it may do so by sending an ldrq# message with the act bit as 0. however, since the dma request was seen by the ich10, there is no assurance that the cycle has not been granted and will shortly run on lpc. therefore, peripherals must take into account that a dma cycle may still occur. the peripheral can choose not to respond to this cycle, in which case the host will abort it, or it can choose to comple te the cycle normally with any random data. this method of dma deassertion should be prevented whenever possible, to limit boundary conditions both on the ich10 and the peripheral. 5.6.3 general flow of dma transfers arbitration for dma channels is performed through the 8237 within the host. once the host has won arbitration on behalf of a dma channel assigned to lpc, it asserts lframe# on the lpc i/f and begins the dma transfer. the general flow for a basic dma transfer is as follows: 1. ich10 starts transfer by asserting 00 00b on lad[3:0] with lframe# asserted. 2. ich10 asserts ?cycle type? of dma, direction based on dma transfer direction. 3. ich10 asserts channel number and, if applicable, terminal count. 4. ich10 indicates the size of the transfer: 8 or 16 bits. 5. if a dma read? ? the ich10 drives the first 8 bits of data and turns the bus around. ? the peripheral acknowledges the data with a valid sync. ? if a 16-bit transfer, the process is repeated for the next 8 bits. 6. if a dma write? ? the ich10 turns the bus around and waits for data. ? the peripheral indicates data ready th rough sync and transfers the first byte. ? if a 16-bit transfer, the peripheral indicates data ready and transfers the next byte. 7. the peripheral turns around the bus. 5.6.4 terminal count terminal count is communicated through lad[3] on the same clock that dma channel is communicated on lad[2:0]. this field is th e channel field. terminal count indicates the last byte of transfer, based upon the size of the transfer. for example, on an 8-bit transfer size (size fiel d is 00b), if the tc bit is set, then this is the last byte. on a 16-bit transfer (size fiel d is 01b), if the tc bit is set, then the second byte is the last byte. the peripheral, therefore, must internalize the tc bit when the channel field is communicated, and only signal tc when the last byte of that transfer size has been transferred. http://www..net/ datasheet pdf - http://www..net/ datasheet 117 functional description 5.6.5 verify mode verify mode is supported on the lpc interfac e. a verify transfer to the peripheral is similar to a dma write, where the peripheral is transferring data to main memory. the indication from the host is the same as a dma write, so the peripheral will be driving data onto the lpc interface. however, the ho st will not transfer this data into main memory. 5.6.6 dma request deassertion an end of transfer is communicated to the ich10 through a special sync field transmitted by the peripheral. an lpc device must not attempt to signal the end of a transfer by deasserting ldreq#. if a dma transfer is several bytes (e.g., a transfer from a demand mode device) the ich10 ne eds to know when to deassert the dma request based on the data currently being transferred. the dma agent uses a sync encoding on each byte of data being transferred, which indicates to the ich10 whether this is the la st byte of transfer or if more bytes are requested. to indicate the last byte of tr ansfer, the peripheral uses a sync value of 0000b (ready with no error), or 1010b (rea dy with error). these encodings tell the ich10 that this is the last piece of da ta transferred on a dma read (ich10 to peripheral), or the byte that follows is the last piece of data transferred on a dma write (peripheral to ich10). when the ich10 sees one of these two encodi ngs, it ends the dma transfer after this byte and deasserts the dma request to the 8237. therefore, if the ich10 indicated a 16-bit transfer, the peripheral can end the tran sfer after one byte by indicating a sync value of 0000b or 1010b. the ich10 does not attempt to transfer the second byte, and deasserts the dma request internally. if the peripheral indicates a 0000b or 1010b sync pattern on the last byte of the indicated size, then the ich10 only deasserts the dma request to the 8237 since it does not need to end the transfer. if the peripheral wishes to keep the dma re quest active, then it uses a sync value of 1001b (ready plus more data). this indicates to the 8237 that more data bytes are requested after the current by te has been transferred, so the ich10 keeps the dma request active to the 8237. therefore, on an 8-bit transfer size, if the peripheral indicates a sync value of 1001b to the ich10, the data will be transferred and the dma request will remain active to the 8237. at a later time, the ich10 will then come back with another start?cyctype?channel?size etc. combination to initiate another transfer to the peripheral. the peripheral must not assume that the next start indication from the ich10 is another grant to the peripheral if it had in dicated a sync value of 1001b. on a single mode dma device, the 8237 will re-arbitrate after every transfer. only demand mode dma devices can be assured that they will re ceive the next start indication from the ich10. note: indicating a 0000b or 1010b encoding on the sync field of an odd byte of a 16-bit channel (first byte of a 16-bit transfer) is an error condition. note: the host stops the transfer on the lpc bus as indicated, fills the upper byte with random data on dma writes (peripheral to memory), and indicates to the 8237 that the dma transfer occurred, incrementing the 8237?s address and decrementing its byte count. http://www..net/ datasheet pdf - http://www..net/ functional description 118 datasheet 5.6.7 sync field / ldrq# rules since dma transfers on lpc are requested through an ldrq# assertion message, and are ended through a sync field during the dm a transfer, the peripheral must obey the following rule when initiating back-to-back transfers from a dma channel. the peripheral must not assert another message for eight lclks after a deassertion is indicated through the sync field. this is needed to allow the 8237, that typically runs off a much slower internal clock, to see a message deasserted before it is re-asserted so that it can arbitrate to the next agent. under default operation, the host only performs 8-bit transfers on 8-bit channels and 16-bit transfers on 16-bit channels. the method by which this communication between host and peripheral through system bios is performed is beyond the scope of th is specification. since the lpc host and lpc peripheral are motherboard devices, no ?plug-n-play? registry is required. the peripheral must not assume that the host is able to perform transfer sizes that are larger than the size allowed for the dma chan nel, and be willing to accept a size field that is smaller than what it may currently have buffered. to that end, it is recommended that future devices that may appear on the lpc bus, that require higher bandwidth than 8-bit or 16-bit dma allow, do so with a bus mastering interface and not rely on the 8237. 5.7 8254 timers (d31:f0) the ich10 contains three counters that have fixed uses. all registers and functions associated with the 8254 timers are in the core well. the 8254 unit is clocked by a 14.31818 mhz clock. counter 0, system timer this counter functions as the system timer by controlling the state of irq0 and is typically programmed for mode 3 operation. the counter produces a square wave with a period equal to the product of the counter period (838 ns) and the initial count value. the counter loads the initial count value 1 counter period after software writes the count value to the counter i/o address. the counter initially asserts irq0 and decrements the count value by two each counter period. the counter negates irq0 when the count value reaches 0. it then reloads the initial count value and again decrements the initial count value by tw o each counter period. the counter then asserts irq0 when the count value reaches 0, reloads the initial count value, and repeats the cycle, alternately asserting and negating irq0. counter 1, refresh request signal this counter provides the refresh request si gnal and is typically programmed for mode 2 operation and only impacts the period of the ref_toggle bit in port 61. the initial count value is loaded one counter period afte r being written to the counter i/o address. the ref_toggle bit will have a square wave behavior (alternate between 0 and 1) and will toggle at a rate based on the value in the counter. programming the counter to anything other than mode 2 will result in undefined behavior for the ref_toggle bit. counter 2, speaker tone this counter provides the speaker tone and is typically programmed for mode 3 operation. the counter provides a speake r frequency equal to the counter clock frequency (1.193 mhz) divided by the initial count value. the speaker must be enabled by a write to port 061h (see nmi status and control ports). http://www..net/ datasheet pdf - http://www..net/ datasheet 119 functional description 5.7.1 timer programming the counter/timers are programmed in the following fashion: 1. write a control word to select a counter. 2. write an initial count for that counter. 3. load the least and/or most significant byte s (as required by control word bits 5, 4) of the 16-bit counter. 4. repeat with other counters. only two conventions need to be observed when programming the counters. first, for each counter, the control word must be written before the initial count is written. second, the initial count must follow the co unt format specified in the control word (least significant byte only, most significant byte only, or least significant byte and then most significant byte). a new initial count may be written to a counter at any time without affecting the counter's programmed mode. counting is affect ed as described in the mode definitions. the new count must follow the programmed count format. if a counter is programmed to read/write two-byte counts, the following precaution applies: a program must not transfer contro l between writing the first and second byte to another routine which also writes into that same counter. otherwise, the counter will be loaded with an incorrect count. the control word register at port 43h controls the operation of all three counters. several commands are available: ? control word command. specifies which counter to re ad or write, the operating mode, and the count format (binary or bcd). ? counter latch command. latches the current count so that it can be read by the system. the countdown process continues. ? read back command. reads the count value, programmed mode, the current state of the out pins, and the state of the null count flag of the selected counter. ta b l e 5 - 1 2 lists the six operating modes for the interval counters. table 5-12. counter operating modes mode function description 0 out signal on end of count (=0) output is 0. when count goes to 0, output goes to 1 and stays at 1 until co unter is reprogrammed. 1 hardware retriggerable one-shot output is 0. when count goes to 0, output goes to 1 for one clock time. 2 rate generator (divide by n counter) output is 1. output goes to 0 for one clock time, then back to 1 and counter is reloaded. 3square wave output output is 1. output goes to 0 when counter rolls over, and counter is reloaded. output goes to 1 when counter rolls over, and counter is reloaded, etc. 4 software triggered strobe output is 1. output goes to 0 when count expires for one clock time. 5 hardware triggered strobe output is 1. output goes to 0 when count expires for one clock time. http://www..net/ datasheet pdf - http://www..net/ functional description 120 datasheet 5.7.2 reading from the interval timer it is often desirable to read the value of a counter without disturbing the count in progress. there are three methods for readin g the counters: a simple read operation, counter latch command, and the read-bac k command. each is explained below. with the simple read and counter latch command methods, the count must be read according to the programmed format; specific ally, if the counter is programmed for two byte counts, two bytes must be read. the tw o bytes do not have to be read one right after the other. read, write, or programming operations for other counters may be inserted between them. 5.7.2.1 simple read the first method is to perform a simple read operation. the counter is selected through port 40h (counter 0), 41h (counter 1), or 42h (counter 2). note: performing a direct read from the counte r does not return a determinate value, because the counting process is asynchronous to read operations. however, in the case of counter 2, the count can be stopped by writing to the gate bit in port 61h. 5.7.2.2 counter latch command the counter latch command, written to port 43h, latches the count of a specific counter at the time the command is received. this command is used to ensure that the count read from the counter is accurate, pa rticularly when reading a two-byte count. the count value is then read from each count er?s count register as was programmed by the control register. the count is held in the latch until it is re ad or the counter is reprogrammed. the count is then unlatched. this allows reading the contents of the counters on the fly without affecting counting in progress. multiple counter latch commands may be used to latch more than one counter. counter latch commands do not affect the programmed mode of the counter in any way. if a counter is latched and then, some time later, latched again before the count is read, the second counter latch command is ig nored. the count read is the count at the time the first counter latch command was issued. 5.7.2.3 read back command the read back command, written to port 43h, latches the count value, programmed mode, and current states of the out pin and null count flag of the selected counter or counters. the value of the counter and its status may then be read by i/o access to the counter address. the read back command may be used to latch multiple counter outputs at one time. this single command is functionally equiva lent to several counter latch commands, one for each counter latched. each counter's la tched count is held until it is read or reprogrammed. once read, a counter is unlat ched. the other counters remain latched until they are read. if multiple count read back commands are issued to the same counter without reading the count, all but the first are ignored. the read back command may additionally be used to latch status information of selected counters. the status of a counter is accessed by a read from that counter's i/o port address. if multiple counter stat us latch operations are performed without reading the status, all but the first are ignored. http://www..net/ datasheet pdf - http://www..net/ datasheet 121 functional description both count and status of the selected counters may be latched simultaneously. this is functionally the same as issuing two consec utive, separate read back commands. if multiple count and/or status read back co mmands are issued to the same counters without any intervening reads, all but the first are ignored. if both count and status of a counter are la tched, the first read operation from that counter returns the latched status, regardless of which was latched first. the next one or two reads, depending on whether the co unter is programmed for one or two type counts, returns the latched count. subsequent reads return unlatched count. 5.8 8259 interrupt controllers (pic) (d31:f0) the ich10 incorporates the functionality of two 8259 interrupt controllers that provide system interrupts for the isa compatible interrupts. these interrupts are: system timer, keyboard controller, serial ports, parallel ports, floppy disk, mouse, and dma channels. in addition, this interrupt contro ller can support the pci based interrupts, by mapping the pci interrupt onto the compat ible isa interrupt line. each 8259 core supports eight interrupts, numbered 0?7. ta b l e 5 - 1 3 shows how the cores are connected. . the ich10 cascades the slave controller onto the master controller through master controller interrupt input 2. this means th ere are only 15 possible interrupts for the ich10 pic. table 5-13. interrupt controller core connections 8259 8259 input typical interrupt source connected pin / function master 0 internal internal timer / counter 0 output / hpet #0 1 keyboard irq1 via serirq 2 internal slave controller intr output 3 serial port a irq3 via serirq, pirq# 4 serial port b irq4 via serirq, pirq# 5 parallel port / generic irq5 via serirq, pirq# 6 floppy disk irq6 via serirq, pirq# 7 parallel port / generic irq7 via serirq, pirq# slave 0 internal real time clock internal rtc / hpet #1 1 generic irq9 via serirq, sci, tco, or pirq# 2 generic irq10 via serirq, sci, tco, or pirq# 3generic irq11 via serirq, sci, tco, or pirq#, or hpet #2 4ps/2 mouse irq12 via serirq, sci, tco, or pirq#, or hpet #3 5internal state machine output ba sed on processor ferr# assertion. may optionally be used for sci or tco interrupt if ferr# not needed. 6sata sata primary (legacy mode), or via serirq or pirq# 7sata sata secondary (legacy mode) or via serirq or pirq# http://www..net/ datasheet pdf - http://www..net/ functional description 122 datasheet interrupts can individually be programmed to be edge or level, except for irq0, irq2, irq8#, and irq13. note: active-low interrupt sources (e.g., the pirq #s) are inverted inside the ich10. in the following descriptions of the 8259s, the interr upt levels are in reference to the signals at the internal interface of the 8259s, afte r the required inversions have occurred. therefore, the term ?high? indicates ?act ive,? which means ?low? on an originating pirq#. 5.8.1 interrupt handling 5.8.1.1 generating interrupts the pic interrupt sequence involves three bits, from the irr, isr, and imr, for each interrupt level. these bits are used to de termine the interrupt vector returned, and status of any other pending interrupts. ta b l e 5 - 1 4 defines the irr, isr, and imr. 5.8.1.2 acknowledging interrupts the processor generates an interrupt acknowle dge cycle that is translated by the host bridge into a pci interrupt acknowledge cycl e to the ich10. the pic translates this command into two internal inta# pulses expe cted by the 8259 cores. the pic uses the first internal inta# pulse to freeze the state of the interrupts for priority resolution. on the second inta# pulse, the master or slave sends the interrupt vector to the processor with the acknowledged interrupt code. this code is based upon bits [7:3] of the corresponding icw2 register, combined wi th three bits representing the interrupt within that controller. table 5-14. interrupt status registers bit description irr interrupt request register. this bit is set on a low to high transition of the interrupt line in edge mode, and by an active high level in level mode. this bit is set whether or not the interrupt is masked. however, a ma sked interrupt will not generate intr. isr interrupt service register. this bit is set, and the co rresponding irr bit cleared, when an interrupt acknowledge cycle is seen, and the vect or returned is for that interrupt. imr interrupt mask register. this bit determines whethe r an interrupt is masked. masked interrupts will not generate intr. table 5-15. content of interrupt vector byte master, slave interrupt bits [7:3] bits [2:0] irq7,15 icw2[7:3] 111 irq6,14 110 irq5,13 101 irq4,12 100 irq3,11 011 irq2,10 010 irq1,9 001 irq0,8 000 http://www..net/ datasheet pdf - http://www..net/ datasheet 123 functional description 5.8.1.3 hardware/softwa re interrupt sequence 1. one or more of the interrupt request lines (irq) are raised high in edge mode, or seen high in level mode, setting the corresponding irr bit. 2. the pic sends intr active to the processor if an asserted interrupt is not masked. 3. the processor acknowledges the intr and responds with an interrupt acknowledge cycle. the cycle is translated into a pc i interrupt acknowledge cycle by the host bridge. this command is broadcast over pci by the ich10. 4. upon observing its own interrupt acknowle dge cycle on pci, the ich10 converts it into the two cycles that the internal 825 9 pair can respond to. each cycle appears as an interrupt acknowledge pulse on the internal inta# pin of the cascaded interrupt controllers. 5. upon receiving the first internally genera ted inta# pulse, the highest priority isr bit is set and the corresponding irr bit is reset. on the trailing edge of the first pulse, a slave identification code is broadcast by the master to the slave on a private, internal three bit wide bus. the slave controller uses these bits to determine if it must respond with an interrupt vector during the second inta# pulse. 6. upon receiving the second internally ge nerated inta# pulse, the pic returns the interrupt vector. if no interrupt request is present because the request was too short in duration, the pic returns vector 7 from the master controller. 7. this completes the interrupt cycle. in aeoi mode the isr bit is reset at the end of the second inta# pulse. otherwise, the isr bit remains set until an appropriate eoi command is issued at the end of the interrupt subroutine. 5.8.2 initialization command words (icwx) before operation can begin, each 8259 must be initialized. in the ich10, this is a four byte sequence. the four initialization command words are referred to by their acronyms: icw1, icw2, icw3, and icw4. the base address for each 8259 initialization command word is a fixed location in the i/o memory space: 20h for the master controller, and a0h for the slave controller. 5.8.2.1 icw1 an i/o write to the master or slave controller base address with data bit 4 equal to 1 is interpreted as a write to icw1. upon sensin g this write, the ich10 pic expects three more byte writes to 21h for the master controller, or a1h for the slave controller, to complete the icw sequence. a write to icw1 starts the initializati on sequence during which the following automatically occur: 1. following initialization, an interrupt request (irq) input must make a low-to-high transition to generate an interrupt. 2. the interrupt mask register is cleared. 3. irq7 input is assigned priority 7. 4. the slave mode address is set to 7. 5. special mask mode is cleared and status read is set to irr. http://www..net/ datasheet pdf - http://www..net/ functional description 124 datasheet 5.8.2.2 icw2 the second write in the sequence (icw2) is programmed to provide bits [7:3] of the interrupt vector that will be released during an interrupt acknowledge. a different base is selected for each interrupt controller. 5.8.2.3 icw3 the third write in the sequence (icw3) has a different meaning for each controller. ? for the master controller, icw3 is used to indicate which irq input line is used to cascade the slave controller. within the ic h10, irq2 is used. therefore, bit 2 of icw3 on the master controller is set to a 1, and the other bits are set to 0s. ? for the slave controller, icw3 is the sl ave identification code used during an interrupt acknowledge cycle. on interrupt acknowledge cycles, the master controller broadcasts a code to the slave controller if the cascaded interrupt won arbitration on the master controller. the slave controller compares this identification code to the value stored in its icw3, and if it matches, the slave controller assumes responsibility for broadcasting the interrupt vector. 5.8.2.4 icw4 the final write in the sequence (icw4) must be programmed for both controllers. at the very least, bit 0 must be set to a 1 to indicate that the controllers are operating in an intel architecture-based system. 5.8.3 operation command words (ocw) these command words reprogram the interru pt controller to operate in various interrupt modes. ? ocw1 masks and unmasks interrupt lines. ? ocw2 controls the rotation of interrupt priorities when in rotating priority mode, and controls the eoi function. ? ocw3 sets up isr/irr reads, enables/disables the special mask mode (smm), and enables/disables polled interrupt mode. 5.8.4 modes of operation 5.8.4.1 fully nested mode in this mode, interrupt requests are ordered in priority from 0 through 7, with 0 being the highest. when an interrupt is acknow ledged, the highest priority request is determined and its vector placed on the bus. additionally, the isr for the interrupt is set. this isr bit remains set until: the processor issues an eoi command immediately before returning from the service routine; or if in aeoi mode, on the trailing edge of the second inta#. while the isr bit is set, all further interrupts of the same or lower priority are inhibited, while higher levels ge nerate another interrupt. interrupt priorities can be changed in the rotating priority mode. http://www..net/ datasheet pdf - http://www..net/ datasheet 125 functional description 5.8.4.2 special fully-nested mode this mode is used in the case of a system where cascading is used, and the priority has to be conserved within each slave. in this case, the special fully-nested mode is programmed to the master controller. this mode is similar to the fully-nested mode with the following exceptions: ? when an interrupt request from a certain slave is in service, this slave is not locked out from the master's priority logic and further interrupt requests from higher priority interrupts within the slave are recognized by the master and initiate interrupts to the processor. in the normal-nested mode, a slave is masked out when its request is in service. ? when exiting the interrupt service routine, software has to check whether the interrupt serviced was the only one from th at slave. this is done by sending a non- specific eoi command to the slave and then reading its isr. if it is 0, a non- specific eoi can also be sent to the master. 5.8.4.3 automatic rotation mode (equal priority devices) in some applications, there are a number of interrupting devices of equal priority. automatic rotation mode provides for a sequential 8-way rotation. in this mode, a device receives the lowest priority after being serviced. in the worst case, a device requesting an interrupt has to wait until each of seven other devices are serviced at most once. there are two ways to accomplish automatic rotation using ocw2; the rotation on non-specific eoi command (r=1, sl=0, eoi=1) and the rotate in automatic eoi mode which is set by (r=1, sl=0, eoi=0). 5.8.4.4 specific rotation mode (specific priority) software can change interrupt priorities by programming the bottom priority. for example, if irq5 is programmed as the bottom priority device, then irq6 is the highest priority device. the set priority command is issued in ocw2 to accomplish this, where: r=1, sl=1, and lo?l2 is the binary priority level code of the bottom priority device. in this mode, internal status is updated by software control during ocw2. however, it is independent of the eoi command. priority changes can be executed during an eoi command by using the rotate on specific eoi command in ocw2 (r=1, sl=1, eoi=1, and lo?l2=irq level to receive bottom priority. 5.8.4.5 poll mode poll mode can be used to conserve space in the interrupt vector table. multiple interrupts that can be serviced by one inte rrupt service routine do not need separate vectors if the service routine uses the poll command. poll mode can also be used to expand the number of interrupts. the po lling interrupt service routine can call the appropriate service routine, instead of prov iding the interrupt vectors in the vector table. in this mode, the intr output is not used and the microprocessor internal interrupt enable flip-flop is reset, disabling its interrupt input. service to devices is achieved by software using a poll command. the poll command is issued by setting p=1 in ocw3. the pic treats its next i/o read as an interrupt acknowledge, sets the appropriat e isr bit if there is a request, and reads the priority level. interrupts are frozen from the ocw3 write to the i/o read. the byte returned during the i/o read contains a 1 in bit 7 if there is an interrupt, and the binary code of the highest priority level in bits 2:0. http://www..net/ datasheet pdf - http://www..net/ functional description 126 datasheet 5.8.4.6 cascade mode the pic in the ich10 has one master 82 59 and one slave 8259 cascaded onto the master through irq2. this configuration can handle up to 15 separate priority levels. the master controls the slaves through a three bit internal bus. in the ich10, when the master drives 010b on this bus, the slave controller takes responsibility for returning the interrupt vector. an eoi command must be issued twice: once for the master and once for the slave. 5.8.4.7 edge and level triggered mode in isa systems this mode is programmed using bit 3 in icw1, which sets level or edge for the entire controller. in the ich10, this bit is disabled and a new register for edge and level triggered mode selection, per interru pt input, is included. this is the edge/ level control registers elcr1 and elcr2. if an elcr bit is 0, an interrupt request w ill be recognized by a low-to-high transition on the corresponding irq input. the irq in put can remain high without generating another interrupt. if an elcr bit is 1, an in terrupt request will be recognized by a high level on the corresponding irq input and ther e is no need for an edge detection. the interrupt request must be removed before the eoi command is issued to prevent a second interrupt from occurring. in both the edge and level triggered modes, the irq inputs must remain active until after the falling edge of the first internal in ta#. if the irq input goes inactive before this time, a default irq7 vector is returned. 5.8.4.8 end of interrupt (eoi) operations an eoi can occur in one of two fashions: by a command word write issued to the pic before returning from a service routine, th e eoi command; or automatically when aeoi bit in icw4 is set to 1. 5.8.4.9 normal end of interrupt in normal eoi, software writes an eoi co mmand before leaving the interrupt service routine to mark the interrupt as complete d. there are two forms of eoi commands: specific and non-specific. when a non-specif ic eoi command is issued, the pic clears the highest isr bit of those that are set to 1. non-specific eoi is the normal mode of operation of the pic within the ich10, as the interrupt being serviced currently is the interrupt entered with the interrupt acknowle dge. when the pic is operated in modes that preserve the fully nested structure, software can determine which isr bit to clear by issuing a specific eoi. an isr bit that is masked is not cleared by a non-specific eoi if the pic is in the special mask mode. an eoi command must be issued for both the master and slave controller. 5.8.4.10 automatic end of interrupt mode in this mode, the pic automatically performs a non-specific eoi operation at the trailing edge of the last interrupt acknowle dge pulse. from a system standpoint, this mode should be used only when a nested mu lti-level interrupt structure is not required within a single pic. the aeoi mode can only be used in the master controller and not the slave controller. http://www..net/ datasheet pdf - http://www..net/ datasheet 127 functional description 5.8.5 masking interrupts 5.8.5.1 masking on an indi vidual interr upt request each interrupt request can be masked individually by the interrupt mask register (imr). this register is programmed through ocw1. each bit in the imr masks one interrupt channel. masking irq2 on the master controller masks all requests for service from the slave controller. 5.8.5.2 special mask mode some applications may require an interrupt service routine to dynamically alter the system priority structure during its execution under software control. for example, the routine may wish to inhibit lower priority requests for a portion of its execution but enable some of them for another portion. the special mask mode enables all interrupts not masked by a bit set in the mask register. normally, when an interrupt servic e routine acknowledges an interrupt without issuing an eoi to clear the isr bit, the interrupt controller inhibits all lower priority requests. in the special mask mode, any interrupts may be selectively enabled by loading the mask register with the appropriate pattern. the special mask mode is set by ocw3 where: ssmm=1, smm=1, and cleared where ssmm=1, smm=0. 5.8.6 steering pci interrupts the ich10 can be programmed to allow pirq a#-pirqh# to be routed internally to interrupts 3?7, 9?12, 14 or 15. the assignment is programmable through the pirqx route control registers, located at 60?63h and 68?6bh in device 31:function 0. one or more pirqx# lines can be routed to the same irqx input. if interrupt steering is not required, the route registers can be programmed to disable steering. the pirqx# lines are defined as active low, level sensitive to allow multiple interrupts on a pci board to share a single line across the connector. when a pirqx# is routed to specified irq line, software must change the irq's corresponding elcr bit to level sensitive mode. the ich10 internally inverts the pirqx# line to send an active high level to the pic. when a pci interrupt is routed onto the pic, the selected irq can no longer be used by an active high device (through serirq). however, active low interrupts can share their interrupt with pci interrupts. internal sources of the pirqs, including sci and tco interrupts, cause the external pirq to be asserted. the ich10 receives the pirq input, like all of the other external sources, and routes it accordingly. http://www..net/ datasheet pdf - http://www..net/ functional description 128 datasheet 5.9 advanced programmable interrupt controller (apic) (d31:f0) in addition to the standard isa-compatible pic described in the previous chapter, the ich10 incorporates the apic. while the standard interrupt controller is intended for use in a uni-processor system, apic can be used in either a uni-processor or multi- processor system. 5.9.1 interrupt handling the i/o apic handles interrupts very differently than the 8259. briefly, these differences are: ? method of interrupt transmission. the i/o apic transmits interrupts through memory writes on the normal datapath to the processor, and interrupts are handled without the need for the processor to run an interrupt acknowledge cycle. ? interrupt priority. the priority of interrupts in th e i/o apic is independent of the interrupt number. for example, interrupt 10 can be given a higher priority than interrupt 3. ? more interrupts. the i/o apic in the ich10 supports a total of 24 interrupts. ? multiple interrupt controllers. the i/o apic architecture allows for multiple i/o apic devices in the system with their own interrupt vectors. 5.9.2 interrupt mapping the i/o apic within the ich10 supports 24 apic interrupts. each interrupt has its own unique vector assigned by software. the interrupt vectors are mapped as follows, and match ?config 6? of the multi-processor specification . table 5-16. apic interrupt mapping 1 (sheet 1 of 2) irq # via serirq direct from pin via pci message internal modules 0 no no no cascade from 8259 #1 1yes no yes 2 no no no 8254 counter 0, hpet #0 (legacy mode) 3yes no yes 4yes no yes 5yes no yes 6yes no yes 7yes no yes 8nononortc, hpet #1 (legacy mode) 9 yes no yes option for sci, tco 10 yes no yes option for sci, tco 11 yes no yes hpet #2, option for sci, tco (note2) 12 yes no yes hpet #3 (note 3) 13 no no no ferr# logic 14 yes no yes sata primary (legacy mode) 15 yes no yes sata secondary (legacy mode) http://www..net/ datasheet pdf - http://www..net/ datasheet 129 functional description notes: 1. when programming the polarity of internal interrupt sources on the apic, interrupts 0 through 15 receive active-high internal interrupt sources, while interrupts 16 through 23 receive active-low inte rnal interrupt sources. 2. if irq 11 is used for hpet #2, software should ensure irq 11 is not shared with any other devices to ensure the proper operation of hpet #2. ich10 hardware does not prevent sharing of irq 11. 3. if irq 12 is used for hpet #3, software should ensure irq 12 is not shared with any other devices to ensure the proper operation of hpet #3. ich10 hardware does not prevent sharing of irq 12. 4. pirq[e:h] are multiplexed with gpio pins. interrupts pirq[e:h] will not be exposed if they are configured as gpios. 5.9.3 pci / pci express* message-based interrupts when external devices through pci / pci expr ess wish to generate an interrupt, they will send the message defined in the pci express* base specification, revision 1.0a for generating inta# - intd#. these will be transl ated internal assertions/de-assertions of inta# ? intd#. 5.9.4 front side bus interrupt delivery for processors that support front side bus (fsb) interrupt delivery, the ich10 requires that the i/o apic deliver interrupt message s to the processor in a parallel manner, rather than using the i/o apic serial scheme. this is done by the ich10 writing (via dmi) to a memory location that is snooped by the processor(s). the processor(s) snoop the cycle to know which interrupt goes active. the following sequence is used: 1. when the ich10 detects an interrupt event (active edge for edge-triggered mode or a change for level-triggered mode), it sets or resets the internal irr bit associated with that interrupt. 2. internally, the ich10 requests to use the bus in a way that automatically flushes upstream buffers. this can be internally implemented similar to a dma device request. 3. the ich10 then delivers the message by performing a write cycle to the appropriate address with the appropriate data. the address and data formats are described below in section 5.9.4.4 . note: fsb interrupt delivery compatibility with processor clock control depends on the processor, not the ich10. 16 pirqa# pirqa# yes internal devices are routable; see section 10.1.54 though section 10.1.60 . 17 pirqb# pirqb# 18 pirqc# pirqc# 19 pirqd# pirqd# 20 n/a pirqe# 4 yes option for sci, tco, hpet #0,1,2, 3. other internal devices are routable; see section 10.1.54 through section 10.1.60 . 21 n/a pirqf# 4 22 n/a pirqg# 4 23 n/a pirqh# 4 table 5-16. apic interrupt mapping 1 (sheet 2 of 2) irq # via serirq direct from pin via pci message internal modules http://www..net/ datasheet pdf - http://www..net/ functional description 130 datasheet 5.9.4.1 edge-triggered operation in this case, the ?assert message? is sent when there is an inactive-to-active edge on the interrupt. 5.9.4.2 level-triggered operation in this case, the ?assert message? is sent when there is an inactive-to-active edge on the interrupt. if after the eoi the interrupt is still active, then another ?assert message? is sent to indicate that the interrupt is still active. 5.9.4.3 registers associated with front side bus interrupt delivery capabilities indication: the capability to support front side bus interrupt delivery is indicated via acpi configuration techniques. this involves the bios creating a data structure that gets reported to the acpi configuration software. 5.9.4.4 interrupt message format the ich10 writes the message to pci (and to the host controller) as a 32-bit memory write cycle. it uses the formats shown in ta b l e 5 - 1 7 and ta b l e 5 - 1 8 for the address and data. the local apic (in the processor) has a delivery mode option to interpret front side bus messages as a smi in which case the processor treats the incoming interrupt as a smi instead of as an interrupt. this does not mean that the ich10 has any way to have a smi source from ich10 power management logic cause the i/o apic to send an smi message (there is no way to do this). th e ich10?s i/o apic can only send interrupts due to interrupts which do not include smi, nmi or init. this means that in ia-32/ intel ? 64 based platforms, front side bus interrupt message format delivery modes 010 (smi/pmi), 100 (nmi), and 101 (init) as indicated in this section, must not be used and is not supported. only the hardware pin connection is supported by ich10. : table 5-17. interrupt message address format bit description 31:20 will always be feeh 19:12 destination id: this is the same as bits 63:56 of the i/o redirection table entry for the interrupt associated with this message. 11:4 extended destination id : this is the same as bits 55:48 of the i/o redirection table entry for the interrupt as sociated with this message. 3 redirection hint: this bit is used by the processor host bridge to allow the interrupt message to be redirected. 0 = the message will be deli vered to the agent (process or) listed in bits 19:12. 1 = the message will be delivered to an agen t with a lower interrupt priority this can be derived from bits 10:8 in the data field (see below). the redirection hint bit will be a 1 if bits 10:8 in the delivery mode field associated with corresponding interrupt are encoded as 001 (lowest priority). otherwise, the redirection hint bit will be 0 2 destination mode: this bit is used only the redirect ion hint bit is set to 1. if the redirection hint bit and the destination mode bit are both set to 1, then the logical destination mode is used, and the redirection is limited only to those processors that are part of the logical group as based on the logical id. 1:0 will always be 00. http://www..net/ datasheet pdf - http://www..net/ datasheet 131 functional description 5.9.5 ioxapic a ddress remapping to support intel ? virtualization technology, interrupt messages are required to go through similar address remapping as any other memory request. address remapping allows for domain isolation for interrupts, so a device assigned in one domain is not allowed to generate an interrupt to another domain. the address remapping is based on the bus: device: function field associated with the requests. the internal apic is required to initiate the interrupt message using a unique bus: device: function. ich10 allows bios to program the unique bus: device: function address for the internal apic. this address field does not ch ange the apic functionality and the apic is not promoted as a stand-alone pci device. see device 31: function 0 offset 6ch for additional information. 5.9.6 external interrup t controller support the ich10 supports external apics off of pci express ports, and does not support apics on the pci bus. the eoi special cycl e is only forwarded to pci express ports. table 5-18. interrupt message data format bit description 31:16 will always be 0000h. 15 trigger mode: 1 = level, 0 = edge. same as the corresponding bit in the i/o redirection table for that interrupt. 14 delivery status: 1 = assert, 0 = deassert. only assert messages are sent. this bit is always 1. 13:12 will always be 00 11 destination mode: 1 = logical. 0 = physical. same as the correspondi ng bit in the i/o redirection table for that interrupt. 10:8 delivery mode: this is the same as the correspo nding bits in the i/o redirection table for that interrupt. 000 = fixed 100 = nmi 001 = lowest priority 101 = init 010 = smi/pmi 110 = reserved 011 = reserved 111 = extint 7:0 vector: this is the same as th e corresponding bits in the i/o redirection table for that interrupt. http://www..net/ datasheet pdf - http://www..net/ functional description 132 datasheet 5.10 serial interrupt (d31:f0) the ich10 supports a serial irq scheme. this allows a single signal to be used to report interrupt requests. the signal used to transmit this information is shared between the host, the ich10, and all periph erals that support serial interrupts. the signal line, serirq, is synchronous to pci clock, and follows the sustained tri-state protocol that is used by all pci signals. this means that if a device has driven serirq low, it will first drive it high synchronous to pci clock and release it the following pci clock. the serial irq protocol defines this sustained tri-state signaling in the following fashion: ? s ? sample phase. signal driven low ? r ? recovery phase. signal driven high ? t ? turn-around phase. signal released the ich10 supports a message for 21 serial interrupts. these represent the 15 isa interrupts (irq0?1, 2?15), the four pci inte rrupts, and the control signals smi# and iochk#. the serial irq protocol does not support the additional apic interrupts (20? 23). note: when the sata controller is configured for legacy ide mode, irq14 and irq15 are expected to behave as isa legacy interrupts, which cannot be shared (i.e., through the serial interrupt pin). if irq14 and irq15 are shared with serial interrupt pin, then abnormal system behavior may occur. for example, irq14/15 may not be detected by ich10's interrupt controller. when the sata controller is not running in native ide mode, irq14 and irq15 are used as special interrupts. if the sata controller is in native modes, these interrupts can be mapped to other devices accordingly. 5.10.1 start frame the serial irq protocol has two modes of operation which affect the start frame. these two modes are: continuous, where the ich10 is solely responsible for generating the start frame; and quiet, where a serial irq peripheral is responsible for beginning the start frame. the mode that must first be entered when enabling the serial irq protocol is continuous mode. in this mode, the ich10 asserts the start frame. this start frame is 4, 6, or 8 pci clocks wide based upon the serial irq control register, bits 1:0 at 64h in device 31:function 0 configuratio n space. this is a polling mode. when the serial irq stream enters quiet mode (signaled in the stop frame), the serirq line remains inactive and pulled up between the stop and start frame until a peripheral drives the serirq signal low. the ich10 senses the line low and continues to drive it low for the remainder of the start frame. since the first pci clock of the start frame was driven by the peripheral in this mode, the ich10 drives the serirq line low for 1 pci clock less than in continuous mode. this mode of operation allows for a quiet, and therefore, lower power operation. http://www..net/ datasheet pdf - http://www..net/ datasheet 133 functional description 5.10.2 data frames once the start frame has been initiated, all of the serirq peripherals must start counting frames based on the rising edge of serirq. each of the irq/data frames has exactly 3 phases of 1 clock each: ? sample phase. during this phase, the serirq device drives serirq low if the corresponding interrupt signal is low. if the corresponding interrupt is high, then the serirq devices tri-state the serirq signal. the serirq line remains high due to pull-up resistors (there is no internal pull-up resistor on this signal, an external pull-up resistor is required). a low level during the irq0?1 and irq2?15 frames indicates that an active-high isa interrupt is not being requested, but a low level during the pci int[a:d], smi#, and iochk# frame indicates that an active-low interrupt is being requested. ? recovery phase. during this phase, the device drives the serirq line high if in the sample phase it was driven low. if it was not driven in the sample phase, it is tri-stated in this phase. ? turn-around phase. the device tri-states the serirq line. 5.10.3 stop frame after all data frames, a stop frame is driven by the ich10. the serirq signal is driven low by the ich10 for 2 or 3 pci clocks. th e number of clocks is determined by the serirq configuration register. the number of clocks determines the next mode (see ta b l e 5 - 1 9 ). 5.10.4 specific interrupts not supported via serirq there are three interrupts seen through the serial stream that are not supported by the ich10. these interrupts are generated internally, and are not sharable with other devices within the system. these interrupts are: ? irq0. heartbeat interrupt generated off of the internal 8254 counter 0. ? irq8#. rtc interrupt can only be generated internally. ? irq13. floating point error interrupt generated off of the processor assertion of ferr#. the ich10 ignores the state of these interru pts in the serial stream, and does not adjust their level based on the level seen in the serial stream. table 5-19. stop frame explanation stop frame width next mode 2 pci clocks quiet mode. any serirq device may initiate a start frame 3 pci clocks continuous mode. only the host (intel ? ich10) may initiate a start frame http://www..net/ datasheet pdf - http://www..net/ functional description 134 datasheet 5.10.5 data frame format ta b l e 5 - 2 0 shows the format of the data frames . for the pci interrupts (a?d), the output from the ich10 is and?d with the pc i input signal. this way, the interrupt can be signaled via both the pci interrupt input signal and via the serirq signal (they are shared). table 5-20. data frame format data frame # interrupt clocks past start frame comment 1irq0 2 ignored. irq0 can only be generated via the internal 8524 2irq1 5 3 smi# 8 causes smi# if low. wi ll set the serirq_smi_sts bit. 4irq3 11 5irq4 14 6irq5 17 7irq6 20 8irq7 23 9 irq8 26 ignored. irq8# can only be generated internally. 10 irq9 29 11 irq10 32 12 irq11 35 13 irq12 38 14 irq13 41 ignored. irq13 can only be generated from ferr# 15 irq14 44 not attached to sata logic 16 irq15 47 not attached to sata logic 17 iochck# 50 same as isa iochck# going active. 18 pci inta# 53 drive pirqa# 19 pci intb# 56 drive pirqb# 20 pci intc# 59 drive pirqc# 21 pci intd# 62 drive pirqd# http://www..net/ datasheet pdf - http://www..net/ datasheet 135 functional description 5.11 real time clock (d31:f0) the real time clock (rtc) module provides a battery backed-up date and time keeping device with two banks of static ram with 128 bytes each, although the first bank has 114 bytes for general purpose usage. three interrupt features are available: time of day alarm with once a second to once a month range, periodic rates of 122 s to 500 ms, and end of update cycle notification. seconds, minutes, hours, days, day of week, month, and year are counted. daylight savings compensation is no longer supported. the hour is represented in twelve or twenty-four hour format, and data can be represented in bcd or binary format. the design is functionally compatible with the motorola ms146818b. the time keeping comes from a 32.768 khz oscillating source, which is divided to achieve an update every second. the lower 14 bytes on the lower ram block has very specific functions. the fi rst ten are for time and date information. the next four (0ah to 0dh) are registers, which configure and report rtc functions. the time and calendar data should match the data mode (bcd or binary) and hour mode (12 or 24 hour) as selected in regist er b. it is up to the programmer to make sure that data stored in these locations is within the reasonable values ranges and represents a possible date and time. the exception to these ranges is to store a value of c0?ffh in the alarm bytes to indicate a don?t care situation. all alarm conditions must match to trigger an alarm flag, which co uld trigger an alarm interrupt if enabled. the set bit must be 1 while programming these locations to avoid clashes with an update cycle. access to time and date information is done through the ram locations. if a ram read from the ten time and date bytes is attempted during an update cycle, the value read do not necessarily represent the true contents of those locations. any ram writes under the same conditions are ignored. note: the leap year determination for adding a 29th day to february does not take into account the end-of-the-century exceptions. the logic simply assumes that all years divisible by 4 are leap years. according to the royal observatory greenwich, years that are divisible by 100 are typically not leap year s. in every fourth century (years divisible by 400, like 2000), the 100-year-exception is over-ridden and a leap-year occurs. note that the year 2100 will be the first time in which the current rtc implementation would incorrectly calculate the leap-year. the ich10 does not implement month/year alarms. 5.11.1 update cycles an update cycle occurs once a second, if the set bit of register b is not asserted and the divide chain is properly configured. during this procedure, the stored time and date are incremented, overflow is checked, a ma tching alarm condition is checked, and the time and date are rewritten to the ram locations. the update cycle will start at least 488 s after the uip bit of register a is asserted, and the entire cycle does not take more than 1984 s to complete. the time and date ram locations (0?9) are disconnected from the external bus during this time. to avoid update and data corruption conditions, external ram access to these locations can safely occur at two times. when a upda ted-ended interrupt is detected, almost 999 ms is available to read and write the valid time and date data. if the uip bit of register a is detected to be low, there is at least 488 s before the update cycle begins. warning: the overflow conditions for leap years adjustments are based on more than one date or time item. to ensure proper operation when adjusting the time, the new time and data values should be set at least two seconds before leap year occurs. http://www..net/ datasheet pdf - http://www..net/ functional description 136 datasheet 5.11.2 interrupts the real-time clock interrupt is internally ro uted within the ich10 both to the i/o apic and the 8259. it is mapped to interrupt vect or 8. this interrupt does not leave the ich10, nor is it shared with any other in terrupt. irq8# from the serirq stream is ignored. however, the high performance event timers can also be mapped to irq8#; in this case, the rtc interrupt is blocked. 5.11.3 lockable ram ranges the rtc?s battery-backed ram supports two 8-byte ranges that can be locked via the configuration space. if the locking bits are set, the corresponding range in the ram will not be readable or writable. a write cycle to those locations will have no effect. a read cycle to those locations will not return the location?s actual value (resultant value is undefined). once a range is locked, the range can be unlocked only by a hard reset, which will invoke the bios and allow it to relock the ram range. 5.11.4 century rollover the ich10 detects a rollover when the year byte (rtc i/o space, index offset 09h) transitions form 99 to 00. upon dete cting the rollover, the ich10 sets the newcentury_sts bit (tcobase + 04h, bit 7). if the system is in an s0 state, this causes an smi#. the smi# handler can update registers in the rtc ram that are associated with century value. if the syst em is in a sleep state (s1?s5) when the century rollover occurs, the ich10 also sets the newcentury_sts bit, but no smi# is generated. when the system resumes from the sleep state, bios should check the newcentury_sts bit and update the century value in the rtc ram. 5.11.5 clearing battery-backed rtc ram clearing cmos ram in an ich10-based platform can be done by using a jumper on rtcrst# or gpi. implementations should not attempt to clear cmos by using a jumper to pull vccrtc low. using rtcrst# to clear cmos a jumper on rtcrst# can be used to clear cmos values, as well as reset to default, the state of those configuration bits that reside in the rtc power well. when the rtcrst# is strapped to ground, the rtc_pwr_sts bit (d31:f0:a4h bit 2) will be set and those configuration bits in the rtc power well will be set to their default state. bios can monitor the state of this bit, and manually clear the rtc cmos array once the system is booted. the normal position would cause rtcrst# to be pulled up through a weak pull-up resistor. ta b l e 5 - 2 1 shows which bits are set to their default state when rtcrst# is asserted. this rtcrst# jumper technique allows the jumper to be moved and then replaced?all while the system is powered off. then, once booted, the rtc_pwr_sts can be detected in the set state. http://www..net/ datasheet pdf - http://www..net/ datasheet 137 functional description table 5-21. configuration bits reset by rtcrst# assertion bit name register location bit(s) default state alarm interrupt enable (aie) register b (general configuration) (rtc_regb) i/o space (rtc index + 0bh) 5x alarm flag (af) register c (flag register) (rtc_regc) i/o space (rtc index + 0ch) 5x swsmi_rate_sel general pm configuration 3 register gen_pmcon_3 d31:f0:a4h 7:6 0 slp_s4# minimum assertion width general pm configuration 3 register gen_pmcon_3 d31:f0:a4h 5:4 0 slp_s4# assertion stretch enable general pm configuration 3 register gen_pmcon_3 d31:f0:a4h 3 0 rtc power status (rtc_pwr_sts) general pm configuration 3 register gen_pmcon_3 d31:f0:a4h 2 0 power failure (pwr_flr) general pm configuration 3 register (gen_pmcon_3) d31:f0:a4h 1 0 afterg3_en general pm configuration 3 register gen_pmcon_3 d31:f0:a4h 0 0 power button override status (prbtnor_sts) power management 1 status register (pm1_sts) pmbase + 00h 11 0 rtc event enable (rtc_en) power management 1 enable register (pm1_en) pmbase + 02h 10 0 sleep type (slp_typ) power management 1 control (pm1_cnt) pmbase + 04h 12:10 0 pme_en general purpose event 0 enables register (gpe0_en) pmbase + 2ch 11 0 batlow_en general purpose event 0 enables register (gpe0_en) pmbase + 2ch 10 0 ri_en general purpose event 0 enables register (gpe0_en) pmbase + 2ch 8 0 newcentury_sts tco1 status register (tco1_sts) tcobase + 04h 7 0 intruder detect (intrd_det) tco2 status register (tco2_sts) tcobase + 06h 0 0 to p swa p ( ts ) backed up control register (buc) chipset config registers:offset 3414h 0x http://www..net/ datasheet pdf - http://www..net/ functional description 138 datasheet using a gpi to clear cmos a jumper on a gpi can also be used to clear cmos values. bios would detect the setting of this gpi on system boot-up, and manually clear the cmos array. note: the gpi strap technique to clear cmos requ ires multiple steps to implement. the system is booted with the jumper in ne w position, then powered back down. the jumper is replaced back to the normal position, then the system is rebooted again. warning: do not implement a jumper on vccrtc to clear cmos. 5.12 processor interface (d31:f0) the ich10 interfaces to the proc essor with a variety of signals ? standard outputs to processor: a20m#, smi#, nmi, init#, intr, stpclk#, ignne#, cpupwrgd, dpslp# ? standard input from processor: ferr#, thrmtrip# most ich10 outputs to the processor use standard buffers. the ich10 has separate v _cpu_io signals that are pulled up at the system level to the processor voltage, and thus determines voh for the outputs to the processor. 5.12.1 processor interface signals this section describes each of the signal s that interface between the ich10 and the processor(s). note that the behavior of some signals may vary during processor reset, as the signals are used for frequency strapping. 5.12.1.1 a20m# (mask a20) the a20m# signal is active (low) when bo th of the following conditions are true: ? the alt_a20_gate bit (bit 1 of port92 register) is a 0 ? the a20gate input signal is a 0 the a20gate input signal is expected to be generated by the external microcontroller (kbc). http://www..net/ datasheet pdf - http://www..net/ datasheet 139 functional description 5.12.1.2 init# (initialization) the init# signal is active (driven low) based on any one of several events described in ta b l e 5 - 2 2 . when any of these events occur, init# is driven low for 16 pci clocks, then driven high. note: the 16-clock counter for init# assertion halts while stpclk# is active. therefore, if init# is supposed to go active while stpclk# is asserted, it actually goes active after stpclk# goes inactive. this section refers to init#, but applies to two signals: init# and init3_3v#, as init3_3v# is functionally identical to init#, but signaling at 3.3 v. 5.12.1.3 ferr#/ignne# (numeric coproc essor error/ ignore numeric error) the ich10 supports the coprocessor error function with the ferr#/ignne# pins. the function is enabled via the coproc_err_en bit (chipset config registers:offset 31ffh: bit 1 for consumer family and offset 31feh: bit 9 for corporate family). ferr# is tied directly to the coprocessor error signal of the processor. if ferr# is driven active by the processor, irq13 goes active (internally). when it detects a write to the coproc_err register (i/o register f0h), the ich10 negates the internal irq13 and drives ignne# active. ignne# remains active until ferr# is driven inactive. ignne# is never driven active unless ferr# is active. table 5-22. init# going active cause of init# going active comment shutdown special cycle from processor observed on ich-(g)mch interconnect (from (g)mch). init# assertion based on value of shutdown policy select register (sps) port92 write, where init_now (bit 0) transitions from 0-to-1. portcf9 write, where sys_rst (bit 1) was a 0 and rst_cpu (bit 2) transitions from 0-to-1. rcin# input signal goes low. rcin# is expected to be driven by the external microcontroller (kbc). 0-to-1 transition on rc in# must occur before the intel ? ich10 will arm init# to be generated again. note: rcin# signal is expected to be low during s3, s4, and s5 states. transition on the rcin# signal in those states (or the transition to those states) may not necessarily cause the init# signal to be generated to the processor. cpu bist to enter bist, software sets cpu_bist_en bit and then does a fu ll processor reset using the cf9 register. http://www..net/ datasheet pdf - http://www..net/ functional description 140 datasheet if coproc_err_en is not set, the assertion of ferr# will not generate an internal irq13, nor will the write to f0h generate ignne#. 5.12.1.4 nmi (non-maskable interrupt) non-maskable interrupts (nmis) can be generated by several sources, as described in ta b l e 5 - 2 3 . 5.12.1.5 stop clock request (stpclk#) the ich10 power management logic controls this active-low signal. refer to section 5.13 for more information on the functionality of this signal. 5.12.1.6 cpu power good (cpupwrgd) this signal is connected to the processor?s pwrgood input. this signal represents a logical and of the ich10?s pwrok and vrmpwrgd signals. 5.12.1.7 deeper sleep (dpslp#) this active-low signal controls the internal gating of the processor?s core clock. this signal asserts before and deasserts after th e stp_cpu# signal to effectively stop the processor?s clock (internally) in the states in which stp_cpu# can be used to stop the processor?s clock externally. figure 5-5. coprocessor error timing diagram ferr# internal irq13 i/o write to f0h ignne# table 5-23. nmi sources cause of nmi comment serr# goes active (either internally, externally via serr # signal, or via message from (g)mch) can instead be routed to generate an sci, through the nmi2sci_en bit (device 31:function 0, tco base + 08h, bit 11). iochk# goes active via serirq# stream (isa system error) can instead be routed to generate an sci, through the nmi2sci_en bit (device 31:function 0, tco base + 08h, bit 11). http://www..net/ datasheet pdf - http://www..net/ datasheet 141 functional description 5.12.2 dual-proce ssor issues 5.12.2.1 signal differences in dual-processor designs, some of the processor signals are unused or used differently than for uniprocessor designs. 5.12.2.2 power management for multiple-processor (or multiple-core) conf igurations in which more than one stop grant cycle may be generated, the (g)mch is expected to count stop grant cycles and only pass the last one through to the ich10. this prevents the ich10 from getting out of sync with the processor on multiple stpclk# assertions. because the s1 state will have the stpclk# signal active, the stpclk# signal can be connected to both processors. however, for acpi implementations, the bios must indicate that the ich10 only supports th e c1 state for dual-processor designs. in going to the s1 state, multiple stop-grant cycles will be generated by the processors. it is assumed that prior to setting the slp_en bit (which causes the transition to the s1 state), the processors will not be executing code that is likely to delay the stop-grant cycles. in going to the s3, s4, or s5 states, the system will appear to pass through the s1 state; thus, stpclk# and slp# are also used . during the s3, s4, and s5 states, both processors will lose power. upon exit from those states, the processors will have their power restored. table 5-24. dp signal differences signal difference a20m# / a20gate generally not used , but still supported by intel ? ich10. stpclk# used for s1 state as well as preparation for entry to s3?s5 also allows for thrm# based throttli ng (not via acpi control methods). should be connected to both processors. ferr# / ignne# generally not used , but still supported by ich10. http://www..net/ datasheet pdf - http://www..net/ functional description 142 datasheet 5.13 power management (d31:f0) 5.13.1 features ? support for advanced configuration and power interface, version 3.0a (acpi) providing power and thermal management ? acpi 24-bit timer ? software initiated throttling of processor performance for thermal and power reduction ? hardware override to throttle processor performance if system too hot ?sci and smi# generation ? acpi c2 state stop-grant state (using stpclk# signal) halts processor?s instruction stream ? pci pme# signal for wake up from low-power states ? system clock control ? acpi c3 state: ability to halt processor clock (but not memory clock) ? acpi c4 state: ability to lower processor voltage. ? system sleep state control ? acpi s1 state: stop grant (using stpclk# signal) halts processor?s instruction stream (only stpclk# active) ? acpi s3 state ? suspend to ram (str) ? acpi s4 state ? suspend-to-disk (std) ? acpi g2/s5 state ? soft off (soff) ? power failure detection and recovery ? intel management engine power management support ? new wake events from the intel mana gement engine (enabled from all s- states including catastrophic s5 conditions) ? streamlined legacy power management for apm-based systems 5.13.2 intel ? ich10 and system power states ta b l e 5 - 2 5 shows the power states defined for ich10-based platforms. the state names generally match the corresponding acpi states. http://www..net/ datasheet pdf - http://www..net/ datasheet 143 functional description ta b l e 5 - 2 6 shows the transitions rules among the various states. note that transitions among the various states may appear to temporarily transition through intermediate states. for example, in going from s0 to s1, it may appear to pass through the g0/s0 states. these intermediate transitions and states are not listed in the table. table 5-25. general power states for systems using intel ? ich10 state/ substates legacy name / description g0/s0/c0 full on: processor operating. individual de vices may be shut down to save power. the different proces sor operating levels are de fined by cx states, as shown in ta b l e 5 - 2 6 . within the c0 state, the intel ? ich10 can throttle the processor using the stpclk# signal to re duce power consumptio n. the throttling can be initiated by software or by the operating system or bios. g0/s0/c1 auto-halt: processor has executed an autohalt instruction and is not executing code. the processor snoops the bus and maintains cache coherency. g0/s0/c2 stop-grant: the stpclk# signal go es active to the processor. the processor performs a stop-grant cycle, halts its in struction stream, and remains in that state until the stpclk# signal goes in active. in the stop-grant state, the processor snoops the bus and maintains cache coherency. g0/s0/c3 stop-clock: the stpclk# signal goes active to the processor. the processor performs a stop-grant cycle, halts its instruction stream. ich10 then asserts dpslp# followed by stp_cpu#, which fo rces the clock generator to stop the processor clock. accesses to memory (by graphics, pci, or internal units) is not permitted while in a c3 state. g0/s0/c4 stop-clock with lower processor voltage: this closely resembles the g0/ s0/c3 state. however, after the ich10 ha s asserted stp_cpu# , it then lowers the voltage to the processor. this reduce s the leakage on the processor. prior to exiting the c4 state, the ich10 increases the voltage to the processor. g1/s1 stop-grant: similar to g0/s0/c2 state. note: the behavior for this state is slig htly different when supporting intel 64 processors. g1/s3 suspend-to-ram (str): the system context is maintained in system dram, but power is shut off to non-critical ci rcuits. memory is re tained, and refreshes continue. all clocks stop except rtc clock. g1/s4 suspend-to-disk (std): the context of the system is maintained on the disk. all power is then shut off to the system except for the logic required to resume. g2/s5 soft off (soff): system context is not maintained. all power is shut off except for the logic required to restart. a full boot is requ ired when waking. g3 mechanical off (moff): system context not maintained. all power is shut off except for the rtc. no ?wake? events are possible, because the system does not have any power. this state occurs if th e user removes the batteries, turns off a mechanical switch, or if the system power supply is at a level that is insufficient to power the ?waking? logic. when system power returns, transition will depend on the state just prior to the entry to g3 and the afterg3 bit in the gen_pmcon3 register (d31:f0 , offset a4). refer to ta b l e 5 - 3 3 for more details. http://www..net/ datasheet pdf - http://www..net/ functional description 144 datasheet notes: 1. some wake events can be pr eserved through power failure. table 5-26. state transi tion rules for intel ? ich10 present state transition trigger next state g0/s0/c0 ? processor halt instruction ?level 2 read ?level 3 read ?level 4 read ?slp_en bit set ? power button override ? mechanical off/power failure ?g0/s0/c1 ?g0/s0/c2 ? g0/s0/c3 or g0/s0/c4 - depending on c4onc3_en bit (d31:f0:offset a0h:bit 7) and bm_sts_zero_en bit (d31:f0:offset a9h:bit 2) ?g1/sx or g2/s5 state ?g2/s5 ?g3 g0/s0/c1 ? any enabled break event ? stpclk# goes active ? power button override ?power failure ?g0/s0/c0 ?g0/s0/c2 ?g2/s5 ?g3 g0/s0/c2 ? any enabled break event ? power button override ?power failure ? previously in c3/c4 and bus masters idle ?g0/s0/c0 ?g2/s5 ?g3 ? c3 or c4 - depending on pdme bit (d31:f0: offset a9h: bit 4) g0/s0/c3 ? any enabled break event ? any bus master event ? power button override ?power failure ? previously in c4 and bus masters idle ?g0/s0/c0 ? g0/s0/c2 - if pume bit (d31:f0: offset a9h: bit 3) is set, else g0/s0/c0 ?g2/s5 ?g3 ? c4 - depending on pdme bit (d31:f0: offset a9h: bit 4 g0/s0/c4 ? any enabled break event ? any bus master event ? power button override ?power failure ?g0/s0/c0 ? g0/s0/c2 - if pume bit (d31:f0: offset a9h: bit 3) is set, else g0/s0/c0 ?g2/s5 ?g3 g1/s1, g1/s3, or g1/s4 ? any enabled wake event ? power button override ?power failure ?g0/s0/c0 ?g2/s5 ?g3 g2/s5 ? any enabled wake event ?power failure ?g0/s0/c0 ?g3 g3 ? power returns ? optional to go to s0/c0 (reboot) or g2/ s5 (stay off until power button pressed or other wake event). (see note 1) http://www..net/ datasheet pdf - http://www..net/ datasheet 145 functional description 5.13.3 system power planes the system has several independent power planes, as described in ta b l e 5 - 2 7 . note that when a particular power plane is shut off, it should go to a 0 v level. s 5.13.4 smi#/sci generation on any smi# event taking place, ich10 assert s smi# to the processor, which causes it to enter smm space. smi# remains active unt il the eos bit is set. when the eos bit is set, smi# goes inactive for a minimum of 4 pci clocks. if another smi event occurs, smi# is driven active again. the sci is a level-mode interrupt that is ty pically handled by an acpi-aware operating system. in non-apic systems (which is the de fault), the sci irq is routed to one of the 8259 interrupts (irq 9, 10, or 11). the 8 259 interrupt controller must be programmed to level mode for that interrupt. in systems using the apic, the sci can be rout ed to interrupts 9, 10, 11, 20, 21, 22, or 23. the interrupt polarity changes depending on whether it is on an interrupt shareable with a pirq or not (see section 13.1.3 ). the interrupt remains asserted until all sci sources are removed. ta b l e 5 - 2 8 shows which events can cause an smi# and sci. note that some events can be programmed to cause either an smi# or sci. the usage of the event for sci (instead of smi#) is typically associated wi th an acpi-based system. each smi# or sci source has a corresponding enable and status bit. table 5-27. system power plane plane controlled by description cpu slp_s3# signal the slp_s3# signal can be used to cut the power to the processor completely. the dprslpvr support allows lowering the processor?s voltage during the c4 state. main slp_s3# signal when slp_s3# goes active, power can be shut off to any circuit not required to wake the system from the s3 state. since the s3 state requires that th e memory context be preserved, power must be retained to the main memory. the processor, devices on the pci bus, lpc i/f, and graphics will typically be shut off when the ma in power plane is shut, although there may be small subsections powered. memory slp_s4# signal slp_s5# signal when the slp_s4# goes active, power can be shut off to any circuit not required to wake the system from the s4. since the memory context does not need to be preserved in the s4 state, the power to the memory can also be shut down. when slp_s5# goes active, power can be shut to any circuit not required to wake the system from the s5 state. since the memory context does not need to be preserved in the s5 state, the power to the memory can also be shut. link controller slp_m# this pin is asserted when the mana geability platform goes to moff. depending on the platform, this pin may be used to control the (g)mch, ich controller link power planes, the clock chip power, and the spi flash power. device[n] gpio individual subsystems may have their own power plane. for example, gpio signals may be used to control the power to disk drives, audio amplifiers, or the display screen. http://www..net/ datasheet pdf - http://www..net/ functional description 146 datasheet table 5-28. causes of smi# and sci (sheet 1 of 2) cause sci smi additional enables where reported pme# yes yes pme_en=1 pme_sts pme_b0 (internal, bus 0, pme-capable agents) yes yes pme_b0_en=1 pme_b0_sts pci express* pme messages yes yes pci_exp_en=1 (not enabled for smi) pci_exp_sts pci express hot plug message yes yes hot_plug_en=1 (not enabled for smi) hot_plug_sts power button press yes yes pwrbtn_en=1 pwrbtn_sts power button override (note 7) yes no none prbtnor_sts rtc alarm yes yes rtc_en=1 rtc_sts ring indicate yes yes ri_en=1 ri_sts usb#1 wakes yes yes usb1_en=1 usb1_sts usb#2 wakes yes yes usb2_en=1 usb2_sts usb#3 wakes yes yes usb3_en=1 usb3_sts usb#4 wakes yes yes usb4_en=1 usb4_sts usb#5 wakes yes yes usb5_en=1 usb5_sts usb#6 wakes yes yes usb6_en=1 usb6_sts thrm# pin active yes yes thrm_en=1 thrm_sts acpi timer overflow (2.34 sec.) yes yes tmrof_en=1 tmrof_sts any gpi yes yes gpi[x]_route=10 (sci) gpi[x]_route=01 (smi) gpe0[x]_en=1 gpi[x]_sts gpe0_sts tco sci logic yes no tcosci_en=1 tcosci_sts tco sci message from (g)mch yes no none mchsci_sts tco smi logic no yes tco_en=1 tco_sts tco smi ? year 2000 rollover no yes none newcentury_sts tco smi ? tco timerout no yes none timeout tco smi ? os writes to tco_dat_in register no yes none os_tco_smi tco smi ? message from (g)mch no yes none mchsmi_sts tco smi ? nmi occurred (and nmis mapped to smi) no yes nmi2smi_en=1 nmi2smi_sts tco smi ? intruder# signal goes active no yes intrd_sel=10 intrd_det tco smi 8 ? change of the bioswp bit from 0 to 1 no yes bc.le=1 bioswr_sts http://www..net/ datasheet pdf - http://www..net/ datasheet 147 functional description notes: 1. sci_en must be 1 to enable sci. sci_en must be 0 to enable smi. 2. sci can be routed to cause interrupt 9:11 or 20:23 (20:23 only available in apic mode). 3. gbl_smi_en must be 1 to enable smi. 4. eos must be written to 1 to re-enable smi for the next 1. 5. ich10 must have smi# fully enabled when ich10 is also enabled to trap cycles. if smi# is not enabled in conjunction with the trap enab ling, then hardware behavior is undefined. 6. only gpi[15:0] may generate an smi# or sci. 7. when a power button override first occurs, th e system will transition immediately to s5. the sci will only occur after the next wake to s0 if the residual status bit (prbtnor_sts) is not cleared prior to setting sci_en. 8. this smi is a synchronous event. tco smi ? write attempted to bios no yes bioswp=1 bioswr_sts bios_rls written to yes no gbl_en=1 gbl_sts gbl_rls written to no yes bios_en=1 bios_sts write to b2h register no yes apmc_en = 1 apm_sts periodic timer expires no yes periodic_en=1 periodic_sts 64 ms timer expires no yes sw smi_tmr_en=1 swsmi_tmr_sts enhanced usb legacy support event no yes legacy_usb2_en = 1 legacy_usb2_sts enhanced usb intel specific event no yes intel_usb2_en = 1 intel_usb2_sts uhci usb legacy logic no yes legacy_usb_en=1 legacy_usb_sts serial irq smi reported no yes none serirq_smi_sts device monitors match address in its range no yes none devtrap_sts smbus host controller no yes smb_smi_en host controller enabled smbus host status reg. smbus slave smi message no yes none smbus_smi_sts smbus smbalert# signal active no yes none smbus_smi_sts smbus host notify message received no yes host_notify_intre n smbus_smi_sts host_notify_sts access microcontroller 62h/ 66h no yes mcsmi_en mcsmi_sts slp_en bit written to 1 no yes sm i_on_slp_en=1 smi_on_slp_en_sts usb per-port registers write enable bit changes to 1. no yes usb2_en=1, write_enable_smi_en able=1 usb2_sts, write enable status write attempted to bios no yes bioswpd = 0 bioswr_sts gpio lockdown enable bit changes from ?1? to ?0?. no yes gpio_unlock_smi_e n=1 gpio_unlock_smi_s ts table 5-28. causes of smi# and sci (sheet 2 of 2) cause sci smi additional enables where reported http://www..net/ datasheet pdf - http://www..net/ functional description 148 datasheet pci express ports and the (g)mch (via dm i) have the ability to cause pme using messages. when a pme message is received, ich10 will set th e pci_exp_sts bit. if the pci_exp_en bit is also set, the ich10 can cause an sci via the gpe1_sts register. pci express has a hot-plug mechanism and is capable of generating a sci via the gpe1 register. it is also capable of generating an smi. however, it is not capable of generating a wake event. 5.13.5 dynamic proces sor clock control the ich10 has extensive control for dynamica lly starting and stopping system clocks. the clock control is used for transitions among the various s0/cx states, and processor throttling. each dynamic clock control method is described in this section. the various sleep states may also perform types of non-dynamic clock control. the ich10 supports the acpi c0 , c1, c2, c3, and c4 states. the dynamic processor clock control is handled using the following signals: ? stpclk#: used to halt processor instruction stream. ? stp_cpu#: used to stop processor?s clock ? dpslp#: used to force deeper sleep for processor. ? dprslpvr: used to lower voltage of vrm during c4 state. ? dprstp#: used to alert the processor of c4 state. also works in conjunction with dprslpvr to communicate to the vrm whether a slow or fast voltage ramp should be used. the c1 state is entered based on the processor performing an auto halt instruction. the c2 state is entered based on the processor reading the level 2 register in the ich10. the c2 state can also be entered from c3 or c4 states if bus masters require snoops and the pume bit (d31:f0: offset a9h: bit 3) is set. the c3 state is entered based on the processor reading the level 3 register in the ich10 and when the c4onc3_en bit is clear (d31:f0:offset a0:bit 7). this state can also be entered after a temporary return to c2 from a prior c3 or c4 state. the c4 state is entered based on the processor reading the level 4 register in the ich10, or by reading the level 3 register wh en the c4onc3_en bit is set. this state can also be entered after a temporary re turn to c2 from a prior c4 state. a c1, c2, c3, or c4 state ends due to a break event. based on the break event, the ich10 returns the system to c0 state. ta b l e 5 - 2 9 lists the possible break events from c2, c3, or c4. the break events from c1 are indicated in the processor?s datasheet. http://www..net/ datasheet pdf - http://www..net/ datasheet 149 functional description 5.13.5.1 slow c4 exit in order to eliminate the audible noise caused by aggressive voltage ramps when exiting c4 the states at a regular, periodic frequency, the ich10 supports a method to slow down the voltage ramp at the processor vr for certain break events. if enabled for this behavior, the ich10 treats irq0 and irq8 as ?slow? break events since both of these can be the system timer tick interrupt. rather than carefully tracking the interrupt and timer configuration information to track the one correct interrupt, it was deemed acceptable to simplify the logic an d slow the break exit sequence for both interrupts. other break event sources invoke the normal exit timings. the ich10 indicates that a slow voltage ramp is desired by deasserting dprstp# (high) and leaving dprslpvr asserted (h igh). the normal voltage ramp rate is communicated by deasserting dprstp# (h igh) and deasserting dprslpvr (low). the ich10 waits an additional delay before starting the normal voltage ramp timer during the c4 or c5 exit sequence. if a ?fas t? break event occurs during the additional, slow-exit time delay, the ich10 quickly de asserts dprslpvr (low ), thereby speeding up the voltage ramp and reducing the delay to a value that is typically seen by the device in the past. in the event that a fast break event and a slow break event occur together, the fast flow is taken. table 5-29. break events event breaks from comment any unmasked interrupt goes active c2 irq[0:15] when using the 8259s, irq[0:23] for i/o apic. since sci is an interrupt, any sci will also be a break event. any internal event that cause an nmi or smi# c2 many possible sources any internal event that cause init# to go active c2 could be indicated by th e keyboard controller via the rcin input signal. any bus master request (internal, external or dma, or bmbusy#) goes active and bm_rld=1 (d31:f0:offset pmbase+04h: bit 1) c3, c4 need to wake up processor so it can do snoops note: if the pume bit (d31:f0: offset a9h: bit 3) is set, then bus mast er activity will not be treated as a break event. instead, there will be a return only to the c2 state. processor pending break event indication c2 only available if ferr# enabled for break event indication (see ferr# mux enable in gcs, chipset config registers:offset 3410h:bit 6) req-c0 message from (g)mch c2 can be sent at any ti me after the ack-c2 message and before the ack-c0 message, when not in c0 state. http://www..net/ datasheet pdf - http://www..net/ functional description 150 datasheet 5.13.5.2 transition rules among s0/cx and throttling states the following priority rules and assumptions apply among the various s0/cx and throttling states: ? entry to any s0/cx state is mutually exclusive with entry to any s1?s5 state. this is because the processor can only perform one register access at a time and sleep states have higher priority than thermal throttling. ? when the slp_en bit is set (system going to a s1 - s5 sleep state), the thtl_en and force_thtl bits can be internally treated as being disabled (no throttling while going to sleep state). ? if the thtl_en or force_thtl bits are set, and a level 2, level 3 or level 4 read then occurs, the system should immediately go and stay in a c2, c3 or c4 state until a break event occurs. a level 2, level 3 or level 4 read has higher priority than the software initiated throttling. ? after an exit from a c2, c3 or c4 state (due to a break event), and if the thtl_en or force_thtl bits are still set the syst em will continue to throttle stpclk#. depending on the time of break event, the first transition on stpclk# active can be delayed by up to one thrm period (1024 pci clocks = 30.72 s). ? the host controller must post stop-grant cycles in such a way that the processor gets an indication of the end of the special cycle prior to the ich10 observing the stop-grant cycle. this ensures that the stpclk# signals stays active for a sufficient period after the proce ssor observes the response phase. ? if in the c1 state and the stpclk# signal goes active, the processor will generate a stop-grant cycle, and the system should go to the c2 state. when stpclk# goes inactive, it should return to the c1 state. 5.13.5.3 deferred c3/c4 due to the new dmi protocol, if there is any bus master activity (other than true isochronous), then the c0 to c3 transition will pause at the c2 state. ich10 will keep the processor in a c2 state until: ? ich10 sees no bus master activity. ? a break event occurs. in this case, the ich10 will perform the c2 to c0 sequence. note that bus master traffic is not a break event in this case. to take advantage of the deferred c3/c4 mode, the bm_sts_zero_en bit must be set. this will cause the bm_sts bit to read as 0 even if some bus master activity is present. if this is not done, then the software may avoid even attempting to go to the c3 or c4 state if it sees the bm_sts bit as 1. if the pume bit (d31:f0: offset a9h: bit 3) is 0, then the ich10 will treat bus master activity as a break event. when reaching the c2 state, if there is any bus master activity, the ich10 will return the processor to a c0 state. 5.13.5.4 popup (auto c3/c4 to c2) when the pume bit (d31:f0: offset a9h: bit 3) is set, the ich10 enables a mode of operation where standard (non-isochronous) bus master activity will not be treated as a full break event from the c3 or c4 states. instead, these will be treated merely as bus master events and return the platform to a c2 state, and thus allow snoops to be performed. after returning to the c2 state, the bus mast er cycles will be sent to the (g)mch, even if the arb_dis bit is set. http://www..net/ datasheet pdf - http://www..net/ datasheet 151 functional description 5.13.5.5 popdown (auto c2 to c3/c4) after returning to the c2 state from c3/c4, it the pdme bit (d31:f0: offset a9h: bit 4) is set, the platform can return to a c3 or c4 state (depending on where it was prior to going back up to c2). this behaves simila r to the deferred c3/c4 transition, and will keep the processor in a c2 state until: ? bus masters are no longer active. ? a break event occurs. note: bus master traffic is not a break event in this case. 5.13.6 sleep states 5.13.6.1 sleep state overview the ich10 directly supports different slee p states (s1?s5), which are entered by setting the slp_en bit, or due to a power bu tton press. the entry to the sleep states is based on several assumptions: ? entry to a cx state is mutually exclusive with entry to a sleep state. this is because the processor can only perform one register access at a time. a request to sleep always has higher priority than throttling. ? prior to setting the slp_en bit, the software turns off processor-controlled throttling. note that thermal throttling ca nnot be disabled, but setting the slp_en bit disables thermal throttling (since s1?s5 sleep state has higher priority). ? the g3 state cannot be entered via any software mechanism. the g3 state indicates a complete loss of power. 5.13.6.2 initiating sleep state sleep states (s1?s5) are initiated by: ? masking interrupts, turning off all bus master enable bits, setting the desired type in the slp_typ field, and then setting the slp_en bit. the hardware then attempts to gracefully put the system into the corresponding sleep state. ? pressing the pwrbtn# signal for more than 4 seconds to cause a power button override event. in this case the transiti on to the s5 state is less graceful, since there are no dependencies on observing st op-grant cycles from the processor or on clocks other than the rtc clock. ? assertion of the thrmtrip# signal will cause a transition to the s5 state. this can occur when system is in s0 or s1 state. table 5-30. sleep types sleep type comment s1 intel ich10 asserts the stpclk# signal. this lowers the processor?s power consumption. no snooping is possible in this state. s3 ich10 asserts slp_s3#. the slp_s3# signal controls the power to non-critical circuits. power is only reta ined to devices needed to wake from this sleeping state, as well as to the memory. s4 ich10 asserts slp_s3# and slp_s4#. the slp_s4# signal shuts off the power to the memory subsystem. only devices needed to wake from this state should be powered. s5 same power state as s4. ich10 asse rts slp_s3#, slp_s4# and slp_s5#. http://www..net/ datasheet pdf - http://www..net/ functional description 152 datasheet 5.13.6.3 exiting sleep states sleep states (s1?s5) are exited based on wake events. the wake events forces the system to a full on state (s0), although some non-critical subsystems might still be shut off and have to be brought back manually. for example, the hard disk may be shut off during a sleep state, and have to be en abled via a gpio pin before it can be used. upon exit from the ich10-controlled sleep st ates, the wak_sts bit is set. the possible causes of wake events (and th eir restrictions) are shown in ta b l e 5 - 3 1 . notes: 1. this is a wake event from s5 only if the sleep state was entered by setting the slp_en and slp_typ bits via software, or if there is a power failure. 2. if in the s5 state due to a power button override or thrmtrip#, the possible wake events are due to power button, hard reset without cycling (see command type 3 in ta b l e 5 - 5 3 ), hard reset system (see command type 4 in ta b l e 5 - 5 3 ), wake smbus slave message (01h), and me initiated non-maskable wake. table 5-31. causes of wake events cause states can wake from how enabled rtc alarm s1?s5 (note 1) set rtc_en bit in pm1_en register power button s1?s5 always enabled as wake event. (note 2). gpi[0:15] s1?s5 (note 1) gpe0_en register note: gpis that are in the core well are not capable of waking the system from slee p states when the core well is not powered. classic usb s1?s4 set usb1_en, usb 2_en, usb3_en, usb4_en, usb5_en, and usb6_en bits in gpe0_en register lan s1?s5 will use pme#. wake enable set with lan logic. ri# s1?s5 (note 1) set ri_en bit in gpe0_en register intel ? high definition audio s1?s5 event sets pme_b0_sts bit; pm_b0_en must be enabled. can not wake from s5 state if it was entered due to power failure or power button override. primary pme# s1?s5 (note 1) pme_b0_en bit in gpe0_en register secondary pme# s1?s5 set pme_en bit in gpe0_en register. pci_exp_wake# s1?s5 pci_exp_wake bit (note 3) sata s1 set pme_en bit in gpe0_en register. (note 4) pci_exp pme message s1 must use the pci express* wake# pin rather than messages for wake from s3,s4, or s5. smbalert# s1?s5 always enabled as wake event smbus slave wake message (01h) s1?s5 wake/smi# command always enabled as a wake event. note: smbus slave message can wake the system from s1?s5, as well as from s5 due to power button override. (note 2). smbus host notify message received s1?s5 host_notify_wken bit smbus slave command register. reported in the smb_wak_sts bit in the gpeo_sts register. me non-maskable wake s1?s5 always enabled as wake event. (note 2). http://www..net/ datasheet pdf - http://www..net/ datasheet 153 functional description 3. when the wake# pin is active and the pci ex press device is enabled to wake the system, the ich10 will wake the platform. 4. sata can only trigger a wake event in s1, bu t if pme is asserted prior to s3/s4/s5 entry and software does not clear the pme_b0 _sts, a wake event would still result. it is important to understand that the various gpis have different levels of functionality when used as wake events. the gpis that reside in the core power well can only generate wake events from sleep states where the core well is powered. also, only certain gpis are ?acpi compliant,? meaning that their status and enable bits reside in acpi i/o space. ta b l e 5 - 3 2 summarizes the use of gpis as wake events. the latency to exit the various sleep states varies greatly and is heavily dependent on power supply design, so much so that the exit latencies due to the ich10 are insignificant. 5.13.6.4 pci express* wake# signal and pme event message pci express ports can wake the platform from any sleep state (s1, s3, s4, or s5) using the wake# pin. wake# is treated as a wake event, but does not cause any bits to go active in the gpe_sts register. pci express ports and the (g)mch (via dmi) have the ability to cause pme using messages. when a pme message is receiv ed, ich10 will set the pci_exp_sts bit. 5.13.6.5 sx-g3-sx, ha ndling power failures depending on when the power failure occurs and how the system is designed, different transitions could occur due to a power failure. the after_g3 bit provides the ability to program whether or not the system should boot once power returns after a power loss event. if the policy is to not boot, the system remains in an s5 state (unless previo usly in s4). there are only three possible events that will wake the system after a power failure. 1. pwrbtn#: pwrbtn# is always enabled as a wake event. when rsmrst# is low (g3 state), the pwrbtn_sts bit is reset. when the ich10 exits g3 after power returns (rsmrst# goes high), the pwrbtn # signal is already high (because v cc - standby goes high before rsmrst# goes high) and the pwrbtn_sts bit is 0. 2. ri#: ri# does not have an internal pull-up. therefore, if this signal is enabled as a wake event, it is important to keep this signal powered during the power loss event. if this signal goes low (active), when power returns the ri_sts bit is set and the system interprets that as a wake event. 3. rtc alarm: the rtc_en bit is in the rtc well and is preserved after a power loss. like pwrbtn_sts the rtc_sts bit is cleared when rsmrst# goes low. the ich10 monitors both pwrok and rsmrst# to detect for power failures. if pwrok goes low, the pwrok_flr bit is set. if rsmrst# goes low, pwr_flr is set. note: although pme_en is in the rtc well, this signal cannot wake the system after a power loss. pme_en is cleared by rtcrst#, and pme_sts is cleared by rsmrst#. table 5-32. gpi wake events gpi power well wake from notes gpi[7:0] core s1 acpi compliant gpi[15:8] suspend s1?s5 acpi compliant http://www..net/ datasheet pdf - http://www..net/ functional description 154 datasheet 5.13.7 thermal management the ich10 has mechanisms to assist with managing thermal problems in the system. 5.13.7.1 thrm# signal the thrm# signal is used as a status input for a thermal sensor. based on the thrm# signal going active, the ich10 generates an smi# or sci (depending on sci_en). if the thrm_pol bit is set low, when the thrm# signal goes low, the thrm_sts bit will be set. this is an indicator that the thermal threshold has been exceeded. if the thrm_en bit is set, then when thrm_sts go es active, either an smi# or sci will be generated (depending on the sci_en bit being set). the power management software (bios or acpi) can then take measures to start reducing the temperature. examples includ e shutting off unwanted subsystems, or halting the processor. by setting the thrm_pol bit to high, anothe r smi# or sci can optionally be generated when the thrm# signal goes back high. this allows the software (bios or acpi) to turn off the cooling methods. note: thrm# assertion does not cause a tco event message in s3 or s4. the level of the signal is not reported in the heartbeat message. 5.13.7.2 software initiated passive cooling this mode is initiated by software setting the thtl_en or force_thtl bits. software sets the thtl_dty or thrm_dty bi ts to select throttle ratio and thtl_en or force_thtl bit to enable the throttling. throttling results in stpclk# active for a minimum time of 12.5% and a maximum of 87.5%. the period is 1024 pci clocks. thus, the stpclk# signal can be active for as little as 128 pci clocks or as much as 896 pci clocks. the actual slowdown (and cooling) of the processor depends on the instruction stream, because the processor is allowed to finish the current instruction. furthermore, the ich10 waits for the stop- grant cycle before starting the count of the time the stpclk# signal is active. table 5-33. transition s due to power failure state at power failure afterg3_en bit transition when power returns s0, s1, s3 1 0 s5 s0 s4 1 0 s4 s0 s5 1 0 s5 s0 http://www..net/ datasheet pdf - http://www..net/ datasheet 155 functional description 5.13.7.3 thrm# override software bit the force_thtl bit allows the bios to forc e passive cooling, independent of the acpi software (which uses the thtl_en and thtl_d ty bits). if this bit is set, the ich10 starts throttling using the ratio in the thrm_dty field. when this bit is cleared the ich10 stops throttling, unless the thtl_en bit is set (indicating that acpi software is attempting throttling). if both the thtl_en and force_thtl bits ar e set, then the ich should use the duty cycle defined by the thrm_dty field, not the thtl_dty field. 5.13.7.4 active cooling active cooling involves fans. the gpio signals from the ich10 can be used to turn on/ off a fan. 5.13.8 event input signals and their usage the ich10 has various input signals that trigger specific events. this section describes those signals and how they should be used. 5.13.8.1 pwrbtn# (power button) the ich10 pwrbtn# signal operates as a ?fixed power button? as described in the advanced configuration and power interface, version 2.0b. pwrbtn# signal has a 16 ms de-bounce on the input. the state transition descriptions are included in ta b l e 5 - 3 4 . note that the transitions start as soon as the pwrbtn# is pressed (but after the debounce logic), and does not depend on when the power button is released. note: during the time that the slp_s4# signal is stretched for the minimum assertion width (if enabled), the power button is not a wake event. refer to power button override function section below for further detail. table 5-34. transitions due to power button present state event transition/action comment s0/cx pwrbtn# goes low smi# or sci generated (depending on sci_en, pwrbtn_init_en, pwrbtn_en and glb_smi_en) software typically initiates a sleep state s1?s5 pwrbtn# goes low wake event. transitions to s0 state standard wakeup g3 pwrbtn# pressed none no effect since no power not latched nor detected s0?s4 pwrbtn# held low for at least 4 consecutive seconds unconditional transition to s5 state no dependence on processor (e.g., stop-grant cycles) or any other subsystem http://www..net/ datasheet pdf - http://www..net/ functional description 156 datasheet power button override function (ich10 consumer only) if pwrbtn# is observed active for at least four consecutive seconds, the state machine unconditionally transitions to the g2/s5 state, regardless of present state (s0-s4), even if pwrok is not active. in this case, the transition to the g2/s5 state does not depend on any particular response from th e processor (e.g., a stop-grant cycle), nor any similar dependency from any other subsystem. the pwrbtn# status is readable to check if the button is currently being pressed or has been released. the status is taken after the de-bounce, and is re adable via the pwrbtn_lvl bit. note: the 4-second pwrbtn# assertion should only be used if a system lock-up has occurred. the 4-second timer starts counting when the ich10 is in a s0 state. if the pwrbtn# signal is asserted and held active when the system is in a suspend state (s1-s5), the assertion causes a wake event. once the system has resumed to the s0 state, the 4- second timer starts. note: during the time that the slp_s4# signal is stretched for the minimum assertion width (if enabled by d31:f0:a4h bit 3), the power button is not a wake event. power button override function (ich10 corporate only) if pwrbtn# is observed active for at least four consecutive seconds when in s0/1 or at least nine consecutive seconds when in s3-s4, the state machine unconditionally transitions to the g2/s5 state, even if pwrok is not active. in this case, the transition to the g2/s5 state does not depend on any particular response from the processor (e.g., a stop-grant cycle), nor any similar dependency from any other subsystem. the pwrbtn# status is readable to check if th e button is currently being pressed or has been released. the status is taken after the de-bounce, and is readable via the pwrbtn_lvl bit. note: a 4 to 9 second pwrbtn# assertion should only be used if a system lock-up has occurred. the power button override timer starts counti ng when pwrbtn# is asserted and will be set to 4 seconds when the platform is in s0/s1 and 9 seconds when the platform is in s3-s4 in order to trigger a power button override event. note: during the time that the slp_s3#/slp_s4 # signal is stretched for the minimum assertion width (if enabled in d31:f0:a4h), a power button is not wake event. for this reason, the ich10 corporate will always exte nd the power button override timer to 9 seconds when in s3/s4 to allow for a wake event that is delayed by slp_s3#/slp_s4# stretching to be observed before accident aly triggering a power button override event. sleep button the advanced configuration and power interface, version 2.0b defines an optional sleep button. it differs from the power button in that it only is a request to go from s0 to s1?s4 (not s5). also, in an s5 state, the power button can wake the system, but the sleep button cannot. although the ich10 does not include a specif ic signal designated as a sleep button, one of the gpio signals can be used to crea te a ?control method? sleep button. see the advanced configuration and power interface, version 2.0b for implementation details. http://www..net/ datasheet pdf - http://www..net/ datasheet 157 functional description 5.13.8.2 ri# (ring indicator) the ring indicator can cause a wake event (if enabled) from the s1?s5 states. ta b l e 5 - 3 5 shows when the wake event is generated or ignored in different states. if in the g0/s0/cx states, the ich10 generates an interrupt based on ri# active, and the interrupt will be set up as a break event. note: filtering/debounce on ri# will not be done in ich10. can be in modem or external. 5.13.8.3 pme# (pci power management event) the pme# signal comes from a pci device to request that the system be restarted. the pme# signal can generate an smi#, sci, or optionally a wake event. the event occurs when the pme# signal goes from high to low. no event is caused when it goes from low to high. there is also an internal pme_b0 bit. this is separate from the external pme# signal and can cause the same effect. 5.13.8.4 sys_reset# signal when the sys_reset# pin is detected as active after the 16 ms debounce logic, the ich10 attempts to perform a ?graceful? reset, by waiting up to 25 ms for the smbus to go idle. if the smbus is idle when the pin is detected active, the reset occurs immediately; otherwise, the counter starts. if at any point during the count the smbus goes idle the reset occurs. if, however, the counter expires and the smbus is still active, a reset is forced upon the system ev en though activity is still occurring. once the reset is asserted, it remains assert ed for 5 to 6 ms regardless of whether the sysreset# input remains asserted or not. it cannot occur again until sys_reset# has been detected inactive after the debounce logic, and the system is back to a full s0 state with pltrst# inactive. note that if bit 3 of the cf9h i/o register is set then sys_reset# will result in a full power cycle reset. 5.13.8.5 thrmtrip# signal if thrmtrip# goes active, the processor is indicating an overheat condition, and the ich10 immediately transitions to an s5 state. however, since the processor has overheated, it does not respond to the ich10?s stpclk# pin with a stop grant special cycle. therefore, the ich10 does not wa it for one. immediately upon seeing thrmtrip# low, the ich10 initiates a transi tion to the s5 state, drive slp_s3#, slp_s4#, slp_s5# low, and set the cts bit. the transition looks like a power button override. when a thrmtrip# event occurs, the ich 10 will power down immediately without following the normal s0 -> s5 path. th e ich10 will immediately drive slp_s3#, slp_s4#, and slp_s5# low after sampling thrmtrip# active. if the processor is running extremely hot and is heating up, it is possible (although very unlikely) that components around it, such as the ich10, are no longer executing cycles properly. therefore, if thrmtrip# goes ac tive, and the ich10 is relying on state machine logic to perform the power down, th e state machine may not be working, and the system will not power down. table 5-35. transitions due to ri# signal present state event ri_en event s0 ri# active x ignored s1?s5 ri# active 0 1 ignored wake event http://www..net/ datasheet pdf - http://www..net/ functional description 158 datasheet the ich provides filtering for short low glit ches on the thrmtrip# signal in order to prevent erroneous system shut downs from noise. glitches shorter than 25nsec are ignored. during boot, thrmtrip# is ignored until slp_s3#, pwrok, vrmpwrgd/vgate, and pltrst# are all ?1?. during entry into a powered-down state (due to s3, s4, s5 entry, power cycle reset, etc.) thrmtrip# is ignored until either slp_s3# = 0, or pwrok = 0, or vrmpwrgd/vgate = 0. note: a thermal trip event will: ? set the afterg3_en bit ? clear the pwrbtn_sts bit ? clear all the gpe0_en register bits ? clear the smb_wak_sts bit only if smb_sak_sts was set due to smbus slave receiving message and not set due to smbalert 5.13.8.6 bmbusy# the bmbusy# signal is an input from a graphics component to indicate if it is busy. if prior to going to the c3 state, the bmbusy# signal is active, then the bm_sts bit will be set. if after going to the c3 state, th e bmbusy# signal goes back active, the ich10 will treat this as if one of the pci req# sign als went active. this is treated as a break event. 5.13.9 alt access mode before entering a low power state, several registers from powered down parts may need to be saved. in the majority of cases, this is not an issue, as registers have read and write paths. however, several of the isa compatible registers are either read only or write only. to get data out of write-only registers, and to restore data into read-only registers, the ich10 implements an alt access mode. if the alt access mode is entered and exited after reading the registers of the ich10 timer (8254), the timer starts counting fa ster (13.5 ms). the following steps listed below can cause problems: 1. bios enters alt access mode for read ing the ich10 timer related registers. 2. bios exits alt access mode. 3. bios continues through the execution of other needed steps and passes control to the operating system. after getting control in step #3, if the oper ating system does not reprogram the system timer again, the timer ticks may be happeni ng faster than expected. for example dos and its associated software assume that the system timer is running at 54.6 ms and as a result the time-outs in the software may be happening faster than expected. operating systems (e.g., microsoft window s* 98, windows* 2000, and windows nt*) reprogram the system timer and therefore do not encounter this problem. for some other operating systems (e.g., microsoft ms-dos*) the bios should restore the timer back to 54.6 ms before passing co ntrol to the operating system. if the bios is entering alt access mode before entering the suspend state it is not necessary to restore the timer contents after the exit from alt access mode. http://www..net/ datasheet pdf - http://www..net/ datasheet 159 functional description 5.13.9.1 write only registers with read paths in alt access mode the registers described in ta b l e 5 - 3 6 have read paths in alt access mode. the access number field in the table indicates which register will be returned per access to that port. table 5-36. write only registers with read paths in alt access mode (sheet 1 of 2) restore data restore data i/o addr # of rds access data i/o addr # of rds access data 00h 2 1 dma chan 0 base address low byte 40h 7 1 timer counter 0 status, bits [5:0] 2 dma chan 0 base address high byte 2 timer counter 0 base count low byte 01h 2 1 dma chan 0 base count low byte 3 timer counter 0 base count high byte 2 dma chan 0 base count high byte 4 timer counter 1 base count low byte 02h 2 1 dma chan 1 base address low byte 5 timer counter 1 base count high byte 2 dma chan 1 base address high byte 6 timer counter 2 base count low byte 03h 2 1 dma chan 1 base count low byte 7 timer counter 2 base count high byte 2 dma chan 1 base count high byte 41h 1 timer counter 1 status, bits [5:0] 04h 2 1 dma chan 2 base address low byte 42h 1 timer counter 2 status, bits [5:0] 2 dma chan 2 base address high byte 70h 1 bit 7 = nmi enable, bits [6:0] = rtc address 05h 2 1 dma chan 2 base count low byte c4h 2 1 dma chan 5 base address low byte 2 dma chan 2 base count high byte 2 dma chan 5 base address high byte 06h 2 1 dma chan 3 base address low byte c6h 2 1 dma chan 5 base count low byte 2 dma chan 3 base address high byte 2 dma chan 5 base count high byte 07h 2 1 dma chan 3 base count low byte c8h 2 1 dma chan 6 base address low byte 2 dma chan 3 base count high byte 2 dma chan 6 base address high byte http://www..net/ datasheet pdf - http://www..net/ functional description 160 datasheet notes: 1. the ocw1 register must be read before entering alt access mode. 2. bits 5, 3, 1, and 0 return 0. 08h 6 1 dma chan 0?3 command 2 cah 2 1 dma chan 6 base count low byte 2 dma chan 0?3 request 2 dma chan 6 base count high byte 3 dma chan 0 mode: bits(1:0) = 00 cch 2 1 dma chan 7 base address low byte 4 dma chan 1 mode: bits(1:0) = 01 2 dma chan 7 base address high byte 5 dma chan 2 mode: bits(1:0) = 10 ceh 2 1 dma chan 7 base count low byte 6 dma chan 3 mode: bits(1:0) = 11. 2 dma chan 7 base count high byte 20h 12 1 pic icw2 of master controller d0h 6 1 dma chan 4?7 command 2 2 pic icw3 of master controller 2 dma chan 4?7 request 3 pic icw4 of master controller 3 dma chan 4 mode: bits(1:0) = 00 4 pic ocw1 of master controller 1 4 dma chan 5 mode: bits(1:0) = 01 5 pic ocw2 of master controller 5 dma chan 6 mode: bits(1:0) = 10 6 pic ocw3 of master controller 6 dma chan 7 mode: bits(1:0) = 11. 7 pic icw2 of slave controller 8 pic icw3 of slave controller 9 pic icw4 of slave controller 10 pic ocw1 of slave controller 1 11 pic ocw2 of slave controller 12 pic ocw3 of slave controller table 5-36. write only registers with read paths in alt access mode (sheet 2 of 2) restore data restore data i/o addr # of rds access data i/o addr # of rds access data http://www..net/ datasheet pdf - http://www..net/ datasheet 161 functional description 5.13.9.2 pic reserved bits many bits within the pic are reserved, and must have certain values written in order for the pic to operate properly. therefore, there is no need to return these values in alt access mode. when reading pic registers from 20h and a0h, the reserved bits shall return the values listed in ta b l e 5 - 3 7 . 5.13.9.3 read only registers with write paths in alt access mode the registers described in ta b l e 5 - 3 8 have write paths to them in alt access mode. software restores these values after returning from a powered down state. these registers must be handled special by softwa re. when in normal mode, writing to the base address/count register also writes to the current address/count register. therefore, the base address/count must be written first, then the part is put into alt access mode and the current address/count register is written. table 5-37. pic reserved bits return values pic reserved bits value returned icw2(2:0) 000 icw4(7:5) 000 icw4(3:2) 00 icw4(0) 0 ocw2(4:3) 00 ocw3(7) 0 ocw3(5) reflects bit 6 ocw3(4:3) 01 table 5-38. register write accesses in alt access mode i/o address register write value 08h dma status register for channels 0?3. d0h dma status register for channels 4?7. http://www..net/ datasheet pdf - http://www..net/ functional description 162 datasheet 5.13.10 system power suppli es, planes, and signals 5.13.10.1 power plane control with slp_s3#, slp_s4#, slp_s5# and slp_m# the slp_s3# output signal can be used to cut power to the system core supply, since it only goes active for the suspend-to-ram st ate (typically mapped to acpi s3). power must be maintained to the ich10 suspend well, and to any other circuits that need to generate wake signals from the suspend-to -ram state. during s3 (suspend-to-ram) all signals attached to powered down plans w ill be tri-stated or driven low, unless they are pulled via a pull-up resistor. cutting power to the core may be done via the power supply, or by external fets on the motherboard. the slp_s4# or slp_s5# output signal can be used to cut power to the system core supply, as well as power to the system memory, since the context of the system is saved on the disk. cutting power to the memo ry may be done via the power supply, or by external fets on the motherboard. the slp_s4# output signal is used to remove power to additional subsystems that are powered during slp_s3#. slp_s5# output signal can be used to cut power to the system core supply, as well as power to the system memory, since the context of the system is saved on the disk. cutting power to the memory may be done vi a the power supply, or by external fets on the motherboard. slp_m# output signal can be used to cut power to the controller link, clock chip and spi flash on a platform that supports intel amt. 5.13.10.2 slp_s4# and su spend-to-ram sequencing the system memory suspend voltage regulator is controlled by the glue logic. the slp_s4# signal should be used to remove power to system memory rather than the slp_s5# signal. the slp_s4# logic in the ic h10 provides a mechanism to fully cycle the power to the dram and/or detect if th e power is not cycled for a minimum time. note: to use the minimum dram power-down feature that is enabled by the slp_s4# assertion stretch enable bit (d31:f0:a4h bi t 3), the dram power must be controlled by the slp_s4# signal. http://www..net/ datasheet pdf - http://www..net/ datasheet 163 functional description 5.13.10.3 pwrok signal the pwrok input should go active based on the core supply voltages becoming valid. pwrok should go active no sooner than 99 ms after vcc3_3 and vcc1_5 have reached their nominal values. pwrok must not glitch, even if rsmrst# is low. note: 1. sysreset# is recommended for implementi ng the system reset button. this saves external logic that is needed if the pwrok input is used. additionally, it allows for better handling of the smbus and processor resets, and avoids improperly reporting power failures. 2. pwrok and rsmrst# are sampled using the rtc clock. therefore, low times that are less than one rtc clock period may not be detected by the ich10. 3. in the case of true pwrok failure, pwrok will go low before vrmpwrgd. 4. when pwrok goes inactive, a host power cycle reset will occur. a host power cycle is the assertion of slp_s3#, slp_s4#, an d slp_s5#, and the deassertion of these signals 3-5 seconds later. the intel management engine remains powered throughout this cycle. 5.13.10.4 cpupwrgd signal this signal is connected to the processor?s vrm via the vrmpwrgd signal and is internally and?d with the pwrok signal th at comes from the system power supply. 5.13.10.5 vrmpwrgd signal vrmpwrgd is an input from the regulator indicating that all of the outputs from the regulator are on and within specification. platforms that use the vrmpwrgd signal to start the clock chip plls assume that it asserts milliseconds before pwrok in order to provide valid clocks in time for the pwrok rising. note: when vrmpwrgd goes inactive, a host power cycle reset will occur. a host power cycle is the assertion of slp_s3#, slp_s4#, and slp_s5#, and the deassertion of these signals 3-5 seconds later. the intel management engine remains powered throughout this cycle. 5.13.10.6 drampwrok signal (corporate only) the drampwrok output is sent to the (g)mch as an indication of when dram power is turned off. the (g)mch uses this informatio n as one of the conditions for asserting the ddr3 reset signal. the ich10?s open-drain buffer pulls the si gnal low when slp_s4# is asserted and clpwrok deasserted. http://www..net/ datasheet pdf - http://www..net/ functional description 164 datasheet 5.13.11 clock generators the clock generator is expected to provide the frequencies shown in ta b l e 5 - 3 9 . 5.13.11.1 clock contro l signals from intel ? ich10 to clock synthesizer the clock generator is assumed to have direct connect from the following ich10 signals: ? stp_cpu#: stops processor clocks in c3 and c4 states ? stp_pci#: stops system pci clocks (not the ich10 free-running 33 mhz clock) due to clkrun# protocol ? slp_s3#: expected to drive clock chip pwrdown (through inverter), to stop clocks in s3 to s5. table 5-39. intel ? ich10 clock inputs clock domain frequency source usage sata_clk 100 mhz differential main clock generator used by sata controller. stopped in s3 ? s based on slp_s3# assertion. dmi_clk 100 mhz differential main clock generator used by dmi and pci express*. stopped in s3 ? s5 based on slp_s3# assertion. pciclk 33 mhz main clock generator free-running pci clock to ich10. stopped in s3 ? s5 based on slp_s3# assertion. clk48 48.000 mhz main clock generator used by usb controllers an d intel high definition audio controller. stopped in s3 ? s5 based on slp_s3# assertion. clk14 14.318 mhz main clock generator used by acpi timers. stopped in s3 ? s5 based on slp_s3# assertion. glan_clk 5 to 62.5 mhz platform lan connect lan connect interface and gigabit lan connect interface. control policy is determined by the clock source. http://www..net/ datasheet pdf - http://www..net/ datasheet 165 functional description 5.13.12 legacy power management theory of operation instead of relying on acpi software, legacy power management uses bios and various hardware mechanisms. the scheme relies on th e concept of detecting when individual subsystems are idle, detecting when the whole system is idle, and detecting when accesses are attempted to idle subsystems. however, the operating system is assumed to be at least apm enabled. without apm calls, there is no quick way to know when the system is idle between keystrokes. the ich10 does not support burst modes. 5.13.12.1 apm power management the ich10 has a timer that, when enabled by the 1min_en bit in the smi control and enable register, generates an smi# once per minute. the smi handler can check for system activity by reading the devact_sts regi ster. if none of the system bits are set, the smi handler can increment a software counter. when the counter reaches a sufficient number of consecutive minutes with no activity, the smi handler can then put the system into a lower power state. if there is activity, various bits in the deva ct_sts register will be set. software clears the bits by writing a 1 to the bit position. the devact_sts register allows for monitori ng various internal devices, or super i/o devices (sp, pp, fdc) on lpc or pci, keyb oard controller accesses, or audio functions on lpc or pci. other pci activity can be monitored by checking the pci interrupts. 5.13.13 reset behavior when a reset is triggered, the ich10 will send a warning message to the (g)mch to allow the (g)mch to attempt to complete any outstanding memory cycles and put memory into a safe state before the platform is reset. when the (g)mch is ready, it will send an acknowledge message to the ich10. once the message is received the ich10 asserts pltrst#. the ich10 does not require an acknowledg e message from the (g)mch to trigger pltrst#. a global reset will occur after 4 se conds if an acknowle dge from the (g)mch is not received. note: when the ich10 causes a reset by asserting pltrst# its output signals will go to their reset states as defined in chapter 3 . a reset in which the host platform is rese t and pltrst# is asserted is called a host reset or host partition reset. depending on the trigger a host reset may also result in power cycling see chapter 5-40 for details. if a host reset is triggered and the ich10 times out before receiving an acknowledge message from the (g)mch a global reset with power cycle will occur. a reset in which the host and me partitions of the platform are reset is called a global reset. http://www..net/ datasheet pdf - http://www..net/ functional description 166 datasheet ta b l e 5 - 4 0 shows the various reset triggers. notes: 1. trigger will result in global reset with power cycle if the acknowledge message is not received by the ich10. 2. ich10 does not send warning message to (g)mch, reset o ccurs without delay. 3. ich10 waits for enabled wake event to complete reset. 4. system stays in s5 state. table 5-40. causes of host and global resets trigger host reset without power cycle host reset with power cycle global reset with power cycle write of 0eh to cf9h register when global reset bit = 0b (d31:f0:ach:20) no yes no (note 1) write of 06h to cf9h register when global reset bit = 0b yes no no (note 1) write of 06h or 0eh to cf9h register when global reset bit = 1b no no yes sys_reset# asserted and cf9h bit 3 = 0 yes no no (note 1) sys_reset# asserted and cf9h bit 3 = 1 no yes no (note 1) smbus slave message received for reset with power cycle no yes no (note 1) smbus slave message received for reset without power cycle yes no no (note 1) tco watchdog timer reaches ze ro two times yes no no (note 1) power failure: pwrok signal or vrmpwrgd signal goes inactive or rsmrst# asserts no no yes (note 2) special shutdown cycle from cpu causes cf9h-like pltrst# and cf9h global reset bit = 1 no no yes special shutdown cycle from cpu causes cf9h-like pltrst# and cf9h bit 3 = 1 no yes no (note 2) special shutdown cycle from cpu causes cf9h- like pltrst# and cf9h global reset bit = 0 yes no no (note 1) intel ? management engine triggered host reset without power cycle yes no no (note 1) intel management engine triggered host reset with power cycle no yes no (note 1) intel management engine tr iggered global reset no no yes intel management engine initiated host reset with power down no yes (note 3) no (note 1) intel management engine watchdog timer no yes (note 4) no (note 1) power management watchdog timer no yes (note 4) no (note 1) http://www..net/ datasheet pdf - http://www..net/ datasheet 167 functional description 5.14 system management (d31:f0) the ich10 provides various functions to make a system easier to manage and to lower the total cost of ownership (tco) of th e system. in addition, ich10 provides integrated asf management support, requir es use of spi flash and intel management engine firmware. features and functions can be augmented via external a/d converters and gpio, as well as an external microcontroller. the following features and functions are supported by the ich10: ? processor present detection ? detects if processor fails to fetch the first instruction after reset ? various error detection (such as ecc errors) indicated by host controller ? can generate smi#, sci, serr, nmi, or tco interrupt ? intruder detect input ? can generate tco interrupt or smi# when the system cover is removed ? intruder# allowed to go active in any power state, including g3 ? detection of bad bios flash (fwh or flash on spi) programming ? detects if data on first read is ffh (indicates that bios flash is not programmed) ? ability to hide a pci device ? allows software to hide a pci device in terms of configuration space through the use of a device hide register (see section 10.1.75 ) note: voltage id from the processor can be read via gpi signals. asf functionality with the integrated ich10 asf controller requires a correctly configured system, including an appropriate sku of the ich10 (see section 1.3 ), (g)mch with intel management engine, intel management engine firmware , system bios support, and appropriate platform lan connect device. 5.14.1 theory of operation the system management functions are designed to allow the system to diagnose failing subsystems. the intent of this logic is that some of the system management functionality can be provided without th e aid of an external microcontroller. 5.14.1.1 detecting a system lockup when the processor is reset, it is expected to fetch its first instruction. if the processor fails to fetch the first instruction after reset, the tco timer times out twice and the ich10 asserts pltrst#. http://www..net/ datasheet pdf - http://www..net/ functional description 168 datasheet 5.14.1.2 handling an intruder the ich10 has an input signal, intruder#, that can be attached to a switch that is activated by the system?s case being open. this input has a two rtc clock debounce. if intruder# goes active (after the debouncer ), this will set the intrd_det bit in the tco_sts register. the intrd_sel bits in the tco_cnt register can enable the ich10 to cause an smi# or interrupt. the bios or interrupt handler can then cause a transition to the s5 state by writing to the slp_en bit. the software can also directly read the status of the intruder# signal (high or low) by clearing and then reading the intrd_det bit. th is allows the signal to be used as a gpi if the intruder function is not required. if the intruder# signal goes inactive some point after the intrd_det bit is written as a 1, then the intrd_det signal will go to a 0 when intruder# input signal goes inactive. note that this is slightly different than a classic sticky bit, since most sticky bits would remain active indefinitely when the signal goes active and would immediately go inactive when a 1 is written to the bit. note: the intrd_det bit resides in the ich10?s rtc well, and is set and cleared synchronously with the rtc clock. thus, wh en software attempts to clear intrd_det (by writing a 1 to the bit location) there may be as much as two rtc clocks (about 65 s) delay before the bit is actually cleared. also, the intruder# signal should be asserted for a minimum of 1 ms to ensure that the intrd_det bit will be set. note: if the intruder# signal is still active when software attempts to clear the intrd_det bit, the bit remains set and the smi is ge nerated again immediately. the smi handler can clear the intrd_sel bits to avoid further smis. however, if the intruder# signal goes inactive and then active again, there will not be further smis, since the intrd_sel bits would select that no smi# be generated. 5.14.1.3 detecting improper firmware hub programming the ich10 can detect the case where the bios flash is not programmed. this results in the first instruction fetched to have a value of ffh. if this occurs, the ich10 sets the bad_bios bit. the bios flash may resi de in fwh or flash on the spi bus. 5.14.1.4 heartbeat and event reporting via smlink/smbus heartbeat and event reporting via smlink/smbus is no longer supported. the intel amt logic in ich10 can be programmed to generate an interrupt to the intel management engine when an event occurs. the intel management engine will poll the tco registers to gather appropriate bits to send the event message to the gigabit ethernet controller, if intel management engine is programmed to do so. the intel management engine is responsible for sending asf 2.0 messages if programmed to do so. in advanced tco bmc mode, the external micro-controller (bmc) accesses the tco info through smbus. http://www..net/ datasheet pdf - http://www..net/ datasheet 169 functional description 5.14.2 tco modes 5.14.2.1 tco legacy/compatible mode in tco legacy/compatible mode the intel ma nagement engine and intel amt logic and smbus controllers are disabled. to enable legacy/compatible tco mode the tcomode bit 7 in the ichstrp0 register in the spi device must be 0. note: smbus and smlink may be tied together ex ternally, if a device has a single smbus interface and needs access to the tco slave and be visisble to the host smbus controller. . figure 5-6. tco legacy/compatible mode smbus configuration host smbus tco slave intel ? ich10 spd (slave) uctrl legacy sensors (master or slave with alert) asf sensors (master or slave) tco compatible mode smbus intel ? me smbus controller 1 intel ? me smbus controller 2 smlink x x http://www..net/ datasheet pdf - http://www..net/ functional description 170 datasheet in tco legacy/compatible mode the intel ich10 can function directly with the integrated gigabit ethernet controller or equivalent external lan controller to report messages to a network management console without the aid of the system processor. this is crucial in cases where the processor is malfunctioning or cannot function due to being in a low-power state. ta b l e 5 - 4 1 includes a list of events that will report messages to the network management console. note: the gpio11/smbalert#/jtagtdo pin will trigger an even t message (when enabled by the gpio11_alert_disable bit) regardless of whether it is configured as a gpi or not. 5.14.2.2 advanced tco mode intel ich10 supports two modes of advanced tco. intel manageability engine (intel me) mode and bmc mode. to enable advance tco mode (intel me or bmc mode) the tcomode bit 7 in the ichstrp0 register in the spi device must be 1. table 5-41. event transitions that cause messages event assertion? deassertion? comments intruder# pin yes no must be in ?s1 or hung s0? state thrm# pin yes yes must be in ?s1 or hung s0? state. note that the thrm# pin is isolated when the core power is of f, thus preventing this event in s3-s5. watchdog timer expired yes no (na) ?s1 or hung s0? state entered gpio[11]/ smbalert# pin yes yes must be in ?s1 or hung s0? state batlow# yes yes must be in ?s1 or hung s0? state cpu_pwr_flr yes no ?s1 or hung s0? state entered http://www..net/ datasheet pdf - http://www..net/ datasheet 171 functional description 5.14.2.2.1 advanced tco intel ? manageability engine mode in this mode, intel me smbus controller 1, host smbus and smlink are connected together internally. see figure 5-7 . this mode is enabled when the bmcmode bit 15 in the ichstrp0 register in the spi device is 0. the intel me smbus controller 2 can be connected to either the smbus pins or the smlink pins by the mesm2sel bit 23 in the ichstrp0 register in the spi device. the default is to have the intel me smbus controller 2 connected to smlink. the intel me smbus controller 2 has no connection to linkalert#. figure 5-7. advanced tco intel ? me smbus/smlink configuration amt smbus controller 1 host smbus intel ? ich10 spd (slave) uctrl legacy sensors (master or slave with alert) asf sensors (master or slave) advanced tco amt mode amt smbus controller 2 smbus tco slave embedded controller smlink intel ? me smbus controller 1 host smbus spd (slave) uctrl legacy sensors (master or slave with alert) asf sensors (master or slave) advanced tco amt mode intel ? me smbus controller 2 smbus tco slave embedded controller smlink http://www..net/ datasheet pdf - http://www..net/ functional description 172 datasheet 5.14.2.2.2 advanced tco bmc mode in this mode, the external microcontroller (bmc) is connected to both smlink and smbus. the bmc communicates with intel management engine through intel me smbus connected to smlink. the host and tco slave communicated with bmc through smbus. see figure 5-8 . this mode is enabled when the bmcmode bit 15 in the ichstrp0 register in the spi device is 1. figure 5-8. advanced tco bmc mode smbus/smlink configuration host smbus tco slave intel ? ich10 spd (slave) legacy sensors (master or slave with alert) asf sensors (master or slave) advanced tco bmc mode intel ? me smbus controller 1 smbus bmc smlink intel ? me smbus controller 2 http://www..net/ datasheet pdf - http://www..net/ datasheet 173 functional description 5.15 general purpose i/o (d31:f0) the ich10 contains up to 61 general purpos e input/output (gpio) signals. each gpio can be configured as an input or output signal. the number of inputs and outputs varies depending on ich10 configuration. 5.15.1 power wells some gpios exist in the suspend power plane. care must be taken to make sure gpio signals are not driven high into powere d-down planes. some ich10 gpios may be connected to pins on devices that exist in the core well. if these gpios are outputs, there is a danger that a loss of core power (pwrok low) or a power button override event results in the ich10 driving a pin to a logic 1 to another device that is powered down. 5.15.2 smi# and sci routing the routing bits for gpio[0:15] allow an input to be routed to smi# or sci, or neither. note that a bit can be routed to either an smi# or an sci, but not both. 5.15.3 triggering gpio[1:15] have ?sticky? bits on the input. refer to the gpe0_sts register. as long as the signal goes active for at least 2 clock cycles, the ich10 keeps the sticky status bit active. the active level can be selected in the gp_lvl register. if the system is in an s0 or an s1 state, the gpi inputs are sampled at 33 mhz, so the signal only needs to be active for about 60 ns to be latched. in the s3?s5 states, the gpi inputs are sampled at 32.768 khz, and thus must be active for at least 61 microseconds to be latched. if the input signal is still active when the latch is cleared, it will again be set. another edge trigger is not required. this makes th ese signals ?level? triggered inputs. 5.15.4 gpio registers lockdown the following gpio registers are locked do wn when the gpio lockdown enable (gle) bit is set. the gle bit resides in d31:f0:gpio control (gc) register. ? offset 00h: gpio_use_sel ? offset 04h: gp_io_sel ? offset 0ch: gp_lvl ? offset 30h: gpio_use_sel2 ? offset 34h: gpi_io_sel2 ? offset 38h: gp_lvl2 ? offset 40h: gpio_use_sel3 (corporate only) ? offset 44h: gpi_io_sel3 (corporate only) ? offset 48h: gp_lvl3 (corporate only) ? offset 60h: gp_rst_sel once these registers are locked down, they become read-only registers and any software writes to these registers will have no effect. to unlock the registers, the gpio lockdown enable (gle) bit is required to be cleared to ?0?. when the gle bit changes from a ?1? to a ?0? a system management interrupt (smi#) is generated if enabled. once the gpio_unlock_smi bit is set, it can not be changed until a pltrst# occurs. http://www..net/ datasheet pdf - http://www..net/ functional description 174 datasheet this ensures that only bios can change th e gpio configuration. if the gle bit is cleared by unauthorized software, bios will set the gle bit again when the smi# is triggered and these registers will continue to be locked down. 5.15.5 serial post codes over gpio ich10 adds the extended capability allowing sy stem software to serialize post or other messages on gpio. this capability negates the requirement for dedicated diagnostic leds on the platform. additionally, based on the newer btx form factors, the pci bus as a target for post codes is increasingly di fficult to support as the total number of pci devices supported are decreasing. 5.15.5.1 theory of operation for the ich10 generation post code serializ ation logic will be shared with gpio. these gpios will likely be shared with led control offered by the super i/o (sio) component. the following reference diagram shows a likely configuration. the anticipated usage model is that either the ich10 or the sio can drive a pin low to turn off an led. in the case of the power led, the sio would normally leave its corresponding pin in a high-z state to allow th e led to turn on. in this state, the ich10 can blink the led by driving its corresponding pin low and subsequently tri-stating the buffer. an external optical sensing device can detect the on/off state of the led. by externally post-processing the information from the optical device, the serial bit stream can be recovered. the hardware will supply a ?sync? byte before the actual data transmission to allow external detection of the transmit frequency. the frequency of transmission should be limited to 1 transition every 1 s to ensure the detector can reliably sample the on/off state of the led. to allow flex ibility in pull-up resistor values for power optimization, the frequency of the transmission is programmable via the drs field in the gp_sb_cmdsts register ( section 13.10.6 ). the serial bit stream is manchester encoded. this choice of transmission ensures that a transition will be seen on every clock. the 1 or 0 data is based on the transmission happening during the high or low phase of the clock. figure 5-9. serial post over gpio reference circuit ich sio v_3p3_stby led r note: the pull-up value is based on the brightness required. http://www..net/ datasheet pdf - http://www..net/ datasheet 175 functional description a simplified hardware/software register interface provides control and status information to track the activity of this block. software enabling the serial blink capability should implement an algorithm re ferenced below to send the serialized message on the enabled gpio. 1. read the go/busy status bit in the gp_sb_cmdsts register and verify it is cleared. this will ensure that the gpio is idled and a previously requested message is still not in progress. 2. write the data to serialize into the gp_sb_data register ( section 13.10.7 ). 3. write the dls and drs values into the gp_sb_cmdsts register and set the go bit. this may be accomplished using a single write. the reference diagram shows the leds being powered from the suspend supply. by providing a generic capability that can be us ed both in the main and the suspend power planes maximum flexibility can be achieved. a key point to make is that the ich will not unintentionally drive the led control pin lo w unless a serialization is in progress. system board connections utilizing this serialization capability are required to use the same power plane controlling the led as th e ich10 gpio pin. otherwise, the ich10 gpio may float low during the message and prevent the led from being controlled from the sio. the hardware will only be se rializing messages when the core power well is powered and the processor is operational. care should be taken to prevent the ich10 fr om driving an active ?1? on a pin sharing the serial led capability. since the sio coul d be driving the line to 0, having the ich drive a 1 would create a high current path. a recommendation to avoid this condition involves choosing a gpio defaulting to an input. the gp_ser_blink register ( section 13.10.7 ) should be set first before changing the direction of the pin to an output. this sequence ensures the open-drain capability of the buffer is properly configured before enabling the pin as an output. 5.15.5.2 serial message format in order to serialize the data onto the gpio, an initial state of high-z is assumed. the sio is required to have its led control pin in a high-z state as well to allow ich10 to blink the led (refer to the reference diagram). the three components of the serial message include the sync, data, and idle fields. the sync field is 7 bits of ?1? data followed by 1 bit of ?0? data. starting from the high-z state (led on) provides external hardware a known initial condition and a known pattern. in case one or more of the leading 1 sync bi ts are lost, the 1s followed by 0 provide a clear indication of ?end of sync?. this patte rn will be used to ?lock? external sampling logic to the encoded clock. the data field is shifted out with the highes t byte first (msb). within each byte, the most significant bit is shifted first (msb). the idle field is enforced by the hardware an d is at least 2 bit times long. the hardware will not clear the busy and go bits until this idle time is met. supporting the idle time in hardware prevents time-based counting in bi os as the hardware is immediately ready for the next serial code when the go bit is cleared. note that the idle state is represented as a high-z condition on the pin. if the last transmitted bit is a 1, returning to the idle state will result in a final 0-1 transition on the output manchester data. two full bit times of idle correspond to a count of 4 time intervals (the width of the time interval is controlled by the drs field). http://www..net/ datasheet pdf - http://www..net/ functional description 176 datasheet the following waveform shows a 1-byte serial write with a data byte of 5ah. the internal clock and bit position are for refere nce purposes only. the manchester d is the resultant data generated and serialized onto the gpio. since the buffer is operating in open-drain mode the transitions are from high-z to 0 and back. 5.15.6 intel management engine gpios the following gpios can be used as cont roller link gpios: gpio9/wol_en, gpio10/ cpu_missing/jtagtms (corporate only), gpio24/mem_led, and gpio57/tpm_pp/ jtagtck (corporate only). controller link gpios are only available on intel amt or asf enabled platforms with supporting intel management engine firmware. controller link gpios are owned by the intel manageme nt engine and are configured by intel management engine firmware. when configured a a controller link gpio the gpio_use_sel bit is ignored. if the controller link gpio is utilized in a platform, its associated gpio functionality is no longer available to the host. if the controller link gpio is not utilized in a platform, the sign al can instead be used as its associated general purpose i/o. 5.16 sata host controller (d31:f2, f5) the sata function in the ich10 has three modes of operation to support different operating system conditions. in the case of native ide enabled operating systems, the ich10 utilizes two controllers to enable all six ports of the bus. the first controller (device 31: function 2) supports ports 0?3 and the second controller (device 31: function 5) supports ports 4 and 5. when using a legacy operating system, only one controller (device 31: function 2) is availabl e that supports ports 0 - 3. in ahci or raid mode, only one controller (device 31: function 2) is used enabling all six ports. the map register, section 15.1.29 , provides the ability to share pci functions. when sharing is enabled, all decode of i/o is done through the sata registers. device 31, function 1 (ide controller) is hidden by software writing to the function disable register (d31, f0, offset f2h, bit 1), and its configuration registers are not used. the ich10 sata controllers feature six sets of interface signals (ports) that can be independently enabled or disabled (they ca nnot be tri-stated or driven low). each interface is supported by an independent dma controller. the ich10 sata controllers interact with an attached mass storage device through a register interface that is equivalent to that presented by a traditional ide host adapter. the host software follows existing standards and conventions when accessing the register interface and follows standard command protocol conventions. note: sata interface transfer rates are independen t of udma mode settings. sata interface transfer rates will operate at the bus?s ma ximum speed, regardless of the udma mode reported by the sata device or the system bios. internal clock manchester d 8-bit sync field (1111_1110) bit 7 0 1 2 3 4 5 6 5a data byte 2 clk idle http://www..net/ datasheet pdf - http://www..net/ datasheet 177 functional description 5.16.1 sata feature support feature ich10 (ahci/raid disabled) ich10 (ahci/raid enabled) native command queuing (ncq) n/a supported auto activate for dma n/a supported hot plug support n/a supported asynchronous signal recovery n/a supported 3 gb/s transfer rate supported supported atapi asynchronous notification n/a supported host & link initiated power management n/a supported staggered spin-up s upported supported command completion coalescing n/a n/a external sata n/a supported feature description native command queuing (ncq) allows the device to reorder co mmands for more efficient data transfers auto activate for dma collapses a dma setup then dma activate sequence into a dma setup only hot plug support allows for device detection wi thout power being applied and ability to connect and discon nect devices without prior notification to the system asynchronous signal recovery provides a recovery from a loss of signal or establishing communication after hot plug 3 gb/s transfer rate capable of data transfers up to 3gb/s atapi asynchronous notification a mechanism for a device to send a notification to the host that the device requires attention host & link initiated power management capability for the host controller or device to re quest partial and slumber interface power states staggered spin-up enables the host the ability to spin up hard drives sequentially to prevent power load problems on boot command completion coalescing reduces interrupt and completi on overhead by allowing a specified number of commands to complete and then generating an interrupt to process the commands external sata technology that allows for an outside the box connection of up to 2 meters (when using the cable defined in sata-io) http://www..net/ datasheet pdf - http://www..net/ functional description 178 datasheet 5.16.2 theory of operation 5.16.2.1 standard ata emulation the ich10 contains a set of registers that shadow the contents of the legacy ide registers. the behavior of the command and control block registers, pio, and dma data transfers, resets, and interrupts are all emulated. note: the ich10 will assert intr when the ma ster device completes the edd command regardless of the command completion status of the slave device. if the master completes edd first, an intr is generated and bsy will remain '1' until the slave completes the command. if the slave comple tes edd first, bsy will be '0' when the master completes the edd command and asserts intr. software must wait for busy to clear (0) before completing an edd command, as required by the ata5 through ata7 (t13) industry standards. 5.16.2.2 48-bit lba operation the sata host controller supports 48-bit lba through the host-to-device register fis when accesses are performed via writes to th e task file. the sata host controller will ensure that the correct data is put into the correct byte of the host-to-device fis. there are special considerations when reading from the task file to support 48-bit lba operation. software may need to read all 16 -bits. since the registers are only 8-bits wide and act as a fifo, a bit must be set in the device/control register, which is at offset 3f6h for primary and 376h for secondary (or their native counterparts). if software clears bit 7 of the control regist er before performing a read, the last item written will be returned from the fifo. if software sets bi t 7 of the control register before performing a read, the first item written will be returned from the fifo. 5.16.3 sata swap bay support the ich10 provides for basic sata swap bay support using the psc register configuration bits and power management fl ows. a device can be powered down by software and the port can then be disabled , allowing removal and insertion of a new device. note: this sata swap bay operation requires bo ard hardware (implementation specific), bios, and operating system support. 5.16.4 hot plug operation ich10 supports hot plug surprise removal an d insertion notification in the partial, slumber and listen mode states when used with low power device presence detection. software can take advantage of power savings in the low power states while enabling hot plug operation. refer to chapter 7 of the ahci specification for details. 5.16.4.1 low power device presence detection low power device presence detection enables sata link power management to co- exist with hot plug (insertion and removal) without interlock switch or cold presence detect. the detection mechanism allows hot pl ug events to be detectable by hardware across all link power states (active, partial, slumber) as well as ahci listen mode. if the low power device presence detection circuit is disabled the ich10 reverts to hot plug surprise removal notification (without an interlock switch) mode that is mutually exclusive of the partial and slumber power management states. http://www..net/ datasheet pdf - http://www..net/ datasheet 179 functional description 5.16.5 function level reset support (flr) the sata host controller supports the function level reset (flr) capability. the flr capability can be used in conjunction with intel virtualization technology. flr allows an operating system in a virtual machine to have complete control over a device, including its initialization, wi thout interfering with the rest of the platform. the device provides a software interface that enable s the operating system to reset the whole device as if a pci reset was asserted. 5.16.5.1 flr steps 5.16.5.1.1 flr initialization 1. a flr is initiated by software writing a ?1? to the initiate flr bit. 2. all subsequent requests targeting the function will not be claimed and will be master abort immediate on the bus. this includes any configuration, i/o or memory cycles, however, the function shall continue to accept completions targeting the function. 5.16.5.1.2 flr operation the function will reset all configuration, i/o and memory registers of the function except those indicated otherwise and reset all internal states of the function to the default or initial condition. 5.16.5.1.3 flr completion the initiate flr bit is reset (cleared) when the flr reset is completed. this bit can be used to indicate to the software that the flr reset is completed. note: from the time initiate flr bit is written to '1' software must wait at least 100 ms before accessing the function. http://www..net/ datasheet pdf - http://www..net/ functional description 180 datasheet 5.16.6 intel ? matrix storage technology configuration the intel ? matrix storage technology offers several diverse options for raid (redundant array of independent disks) to meet the needs of the end user. ahci support provides higher performance and alleviates disk bottlenecks by taking advantage of the independent dma engines that each sata port offers in ich10. ? raid level 0 performance scaling up to 4 drives, enabling higher throughput for data intensive applications such as video editing. ? data security is offered through raid level 1, which performs mirroring. ? raid level 10 provides high levels of storage performance with data protection, combining the fault-tolerance of raid level 1 with the performance of raid level 0. by striping raid level 1 segments, high i/o rates can be achieved on systems that require both performance and fault-tolerance. raid level 10 requires 4 hard drives, and provides the capacity of two drives. ? raid level 5 provides highly efficient storage while maintaining fault-tolerance on 3 or more drives. by striping parity, and rotating it across all disks, fault tolerance of any single drive is achieved while only consuming 1 drive worth of capacity. that is, a 3 drive raid 5 has the capacity of 2 drives, or a 4 drive raid 5 has the capacity of 3 drives. raid 5 has high read transaction rates, with a medium write rate. raid 5 is well suited for applications that require high amounts of storage while maintaining fault tolerance. by using the ich10?s built-in intel matrix st orage technology, there is no loss of pci resources (request/grant pair) or add-in card slot. intel matrix storage technology functionality requires the following items: 1. ich10 component enabled for intel matrix storage technology (see section 1.3 ) 2. intel matrix storage manager raid option rom must be on the platform 3. intel matrix storage manager drivers, most recent revision. 4. at least two sata hard disk drives (minimum depends on raid configuration). intel matrix storage technology is not av ailable in the following configurations: 1. the sata controller is in compatible mode. 5.16.6.1 intel ? matrix storage mana ger raid option rom the intel matrix storage manager raid option rom is a standard pnp option rom that is easily integrated into any system bios. when in place, it provides the following three primary functions: ? provides a text mode user interface that allows the user to manage the raid configuration on the system in a pre-operating system environment. its feature set is kept simple to keep size to a minimum, but allows the user to create & delete raid volumes and select recovery options when problems occur. ? provides boot support when using a raid vo lume as a boot disk. it does this by providing int13 services when a raid volume needs to be accessed by dos applications (such as ntldr) and by ex porting the raid volumes to the system bios for selection in the boot order. ? at each boot up, provides the user with a status of the raid volumes and the option to enter the user interface by pressing ctrl-i. http://www..net/ datasheet pdf - http://www..net/ datasheet 181 functional description 5.16.7 power management operation power management of the ich10 sata controller and ports will cover operations of the host controller and the sata wire. 5.16.7.1 power state mappings the d0 pci power management state for device is supported by the ich10 sata controller. sata devices may also have multiple power states. from parallel ata, three device states are supported through acpi. they are: ? d0 ? device is working and instantly available. ? d1 ? device enters when it receives a standby immediate command. exit latency from this state is in seconds ? d3 ? from the sata device?s perspective, no different than a d1 state, in that it is entered via the standby immediate command. however, an acpi method is also called which will reset the device and then cut its power. each of these device states are subsets of the host controller?s d0 state. finally, sata defines three phy layer power states, which have no equivalent mappings to parallel ata. they are: ? phy ready ? phy logic and pll are both on and active ? partial ? phy logic is powered, but in a reduced state. exit latency is no longer than 10 ns ? slumber ? phy logic is powered, but in a reduced state. exit latency can be up to 10 ms. since these states have much lower exit latency than the acpi d1 and d3 states, the sata controller defines these states as sub-states of the device d0 state. figure 5-10. sata power states intel ? ich sata controller = d0 device = d3 power res ume latency device = d0 phy = ready device = d1 phy = slumber phy = partial phy = off (port disabled) phy = slumber phy = off (port disabled) phy = slumber phy = off (port disabled) http://www..net/ datasheet pdf - http://www..net/ functional description 182 datasheet 5.16.7.2 power state transitions 5.16.7.2.1 partial and slumber state entry/exit the partial and slumber states save interf ace power when the interface is idle. the sata controller defines phy layer power management (as performed via primitives) as a driver operation from the host side, and a device proprietary mechanism on the device side. the sata controller accepts device transition types, but does not issue any transitions as a host. all received requ ests from a sata device will be acked. when an operation is performed to the sata controller such that it needs to use the sata cable, the controller must check whet her the link is in the partial or slumber states, and if so, must issue a com_wake to bring the link back online. similarly, the sata device must perform the same action. 5.16.7.2.2 device d1, d3 states these states are entered after some period of time when software has determined that no commands will be sent to this device for some time. the mechanism for putting a device in these states does not involve any work on the host controller, other then sending commands over the interface to th e device. the command most likely to be used in ata/atapi is the ?standby immediate? command. 5.16.7.2.3 host controller d3 hot state after the interface and device have been pu t into a low power state, the sata host controller may be put into a low power stat e. this is performed via the pci power management registers in configuration space. there are two very important aspects to note when using pci power management. 1. when the power state is d3, only accesses to configuration space are allowed. any attempt to access the memory or i/o spaces will result in master abort. 2. when the power state is d3, no interrupt s may be generated, even if they are enabled. if an interrupt status bit is pending when the controller transitions to d0, an interrupt may be generated. when the controller is put into d3, it is a ssumed that software has properly shut down the device and disabled the ports. therefore, there is no need to sustain any values on the port wires. the interface will be treated as if no device is present on the cable, and power will be minimized. when returning from a d3 state, an internal reset will not be performed. 5.16.7.2.4 non-ahci mode pme# generation when in non-ahci mode (legacy mode) of operation, the sata controller does not generate pme#. this includes attach events (since the port must be disabled), or interlock switch events (via the satagp pins). 5.16.7.3 smi trapping (apm) device 31:function2:offset c0h (see section 14.1.37 ) contain control for generating smi# on accesses to the ide i/o spaces. th ese bits map to the legacy ranges (1f0? 1f7h, 3f6h, 170?177h, and 376h) and native ide ranges defined by pcmdba, pctlba, scmdba an sctlba. if the sata controller is in legacy mode and is using these addresses, accesses to one of these ranges with the appropriate bit set causes the cycle to not be forwarded to the sata controlle r, and for an smi# to be generated. if an access to the bus-master ide registers occurs while trapping is enabled for the device being accessed, then the register is updated, an smi# is generated, and the device activity status bits ( section 14.1.38 ) are updated indicating that a trap occurred. http://www..net/ datasheet pdf - http://www..net/ datasheet 183 functional description 5.16.8 sata device presence in legacy mode, the sata controller does not generate interrupts based on hot plug/ unplug events. however, the sata phy does kn ow when a device is connected (if not in a partial or slumber state), and it s beneficial to communicate this information to host software as this will greatly reduce boot times and resume times. the flow used to indicate sata device presence is shown in figure 5-11 . the ?pxe? bit refers to pcs.p[3:0]e bits, depending on the port being checked and the ?pxp? bits refer to the pcs.p[3:0]p bits, depending on the port being checked. if the pcs/pxp bit is set a device is present, if the bit is cleared a device is not present. if a port is disabled, software can check to see if a new device is connected by periodically reenabling the port and observing if a device is present, if a device is not present it can disable the port and check again later. if a port rema ins enabled, software can periodically poll pcs.pxp to see if a new device is connected. figure 5-11. flow for port enable / device present bits http://www..net/ datasheet pdf - http://www..net/ functional description 184 datasheet 5.16.9 sata led the sataled# output is driven whenever the bsy bit is set in any sata port. the sataled# is an active-low open-drain outp ut. when sataled# is low, the led should be active. when sataled# is high, the led should be inactive. 5.16.10 ahci operation the ich10 provides hardware support for ad vanced host controller interface (ahci), a programming interface for sata host controllers developed through a joint industry effort. ahci defines transactions between the sata controller and software and enables advanced performance and usability with sa ta. platforms supporting ahci may take advantage of performance features such as no master/slave designation for sata devices?each device is treated as a master?and hardware assisted native command queuing. ahci also provides usability enhancements such as hot-plug. ahci requires appropriate software support (e.g., an ahci driver) and for some features, hardware support in the sata device or additional platform hardware. the ich10 supports all of the mandatory features of the serial ata advanced host controller interface specification , revision 1.2 and many optional features, such as hardware assisted native command queuing, aggressive power management, led indicator support, and hot-plug through the use of interlock switch support (additional platform hardware and software may be re quired depending upon the implementation). note: for reliable device removal notification wh ile in ahci operation without the use of interlock switches (surprise removal), interf ace power management should be disabled for the associated port. see section 7.3.1 of the ahci specification for more information. 5.16.11 serial ata referenc e clock low power request (sataclkreq#) the 100 mhz serial ata reference clock (sataclkp, sataclkn) is implemented on the system as a ground-terminated low-voltage differential signal pair driven by the system clock chip. when all the sata links are in slumber or disabled, the sata reference clock is not needed and may be stopped and tri-stated at the clock chip allowing system-level power reductions. the ich10 uses the sataclkreq# output si gnal to communicate with the system clock chip to request either sata clock running or to tell the system clock chip that it can stop the sata reference clock. ich10 drives this signal low to request clock running, and tristates the signal to indicate that the sata reference clock may be stopped (the ich10 never drives the pin high ). when the sataclkreq# is tristated by the ich10, the clock chip may stop the sata reference clock within 100 ns, anytime after 100 ns, or not at all. if the sata re ference clock is not already running, it will start within 100 ns after a sataclkreq# is driven low by the ich10. to enable sata reference clock low power request: 1. configure gpio35 to native function 2. set sata clock request enable (scre) bit to ?1? (dev 31:f2:offset 94h:bit 28). note: the reset default for sataclkreq# is low to insure that the sata reference clock is running after system reset. http://www..net/ datasheet pdf - http://www..net/ datasheet 185 functional description 5.16.12 sgpio signals the sgpio signals, in accordance to the s ff-8485 specification, support per-port led signaling. these signals are not related to sataled#, which allows for simplified indication of sata command activity. the sgpio group interfaces with an external controller chip that fetches and serializes the data for driving across the sgpio bus. the output signals then control the leds. this feature is only valid in ahci/raid mode. 5.16.12.1 mechanism the enclosure management for sata controller 1 (device 31: function 2) involves sending messages that control leds in the enclosure. the messages for this function are stored after the normal registers in the ahci bar, at offset 400h bytes for ich10 from the beginning of the ahci bar as specified by the em_loc global register ( section 14.4.1.8 ). software creates messages for transmission in the enclosure management message buffer. the data in the message buffer should not be changed if ctl.tm bit is set by software to transmit an update message. software should only update the message buffer when ctl.tm bit is cleared by hard ware otherwise the message transmitted will be indeterminate. software then writes a register to cause hardware to transmit the message or take appropriate action based on the message content. the software should only create message types supported by the controller, which is led messages for ich10. if the software creates other non led message types (e.g. saf-te, ses-2), the sgpio interface may hang an d the result is indeterminate. during reset all sgpio pins will be in tri-state state. the interface will continue to be in tri-state state after reset until the first transmission occurs when software programs the message buffer and sets the transmit bit ctl.tm. the sata host controller will initiate the transmission by driving sclock and at the same time drive the sload to ?0? prior to the actual bit stream transmi ssion. the host will drive sload low for at least 5 sclock then only start the bit stre am by driving the sloa d to high. sload will be driven high for 1 sclock follow by vendor specific pattern that is default to ?0000? if software has yet to program the value. a total of 18-bit stream from 6 ports (port0, port1, port2, port3, port4 and port5) of 3- bit per port led message will be transmitted on sdataout0 pin after the sload is driven high for 1 sclock. only 2 ports (port4 and port5) of 6 bit total led message follo w by 12 bits of tri-state value will be transmitted out on sdataout1 pin. all the default led message values will be high prior to software setting them, except the activity led message that is configured to be hardware driven that will be generated based on the activity from the respective port. all the led message values will be driven to ?1? for the port that is unimplemented as indicated in the port implemented register regardless of the software programmed value through the message buffer. there are 2 different ways of resetting ich sgpio interface, asynchronous reset and synchronous reset. asynchronous reset is ca used by platform reset to cause the sgpio interface to be tri-state asynchronously. sy nchronous reset is caused by setting the ctl.reset bit, clearing the ghc.ae bit or hba reset, where host controller will complete the existing full bit stream transmis sion then only tri-state all the sgpio pins. after the reset, both synchronous and as ynchronous, the sgpio pins will stay tri- stated. note: ich host controller does not ensure to cause the target sgpio device or controller to be reset. software is respon sible to keep ich sgpio interface in tri-state stated for 2 second in order to cause a reset on the target of the sgpio interface. http://www..net/ datasheet pdf - http://www..net/ functional description 186 datasheet 5.16.12.2 message format messages shall be constructed with a one dword header that describes the message to be sent followed by the actual message cont ents. the first dword shall be constructed as follows: the saf-te, ses-2, and sgpio message formats are defined in the corresponding specifications, respectively. the led message type is defined in section 5.16.12.3 . it is the responsibility of software to ensure the co ntent of the message format is correct. if the message type is not programmed as 'led' for this controller, the controller shall not take any action to update its leds. note that for led message type, the message size is always consisted of 4 bytes. 5.16.12.3 led message type the led message type specifies the status of up to three leds. typically, the usage for these leds is activity, fault, and locate. no t all implementations necessarily contain all leds (for example, some implementations may not have a locate led). the message identifies the hba port number that the slot status applies to. the format of the led message type is defined in ta b l e 5 - 4 2 . the leds shall retain their values until there is a following update for that particular slot. bit description 31:28 reserved 27:24 message type (mtype): specifies the type of the message. the message types are: 0h = led 1h = saf-te 2h = ses-2 3h = sgpio (register based interface) all other values reserved 23:16 data size (dsize): specifies the data size in bytes. if the message (enclosure services command) has a data buffer that is associated with it that is transferred, the size of that data buffer is specified in this fi eld. if there is no separate data buffer, this field shall have a value of ?0?. the data directly follows the message in the message buffer. for ich10, this va lue should always be ?0?. 15:8 message size (msize): specifies the size of the message in bytes. the message size does not include the one dword header. a value of ?0? is invalid. for ich10, the message size is always 4 bytes. 7:0 reserved http://www..net/ datasheet pdf - http://www..net/ datasheet 187 functional description table 5-42. multi-acti vity led message type byte description 3-2 value (val): this field describes the state of each led for a particular location. there are three leds that may be supported by the hba. each led has 3 bits of control. led values are: 000b - led shall be off 001b - led shall be solid on as perceived by human eye all other values reserved the led bit locations are: bits 2:0 - activity led (may be driven by hardware) bits 5:3 - vendor specific led (e.g. locate) bits 8:6 - vendor specific led (e.g. fault) bits 15:9 - reserved vendor specific message is: bit 3:0 - vendor specific pattern bit 15:4 - reserved note: if activity led hardware driven (att r.alhd) bit is set, host will output the hardware led value sampled internally and will ignore software written activity value on bit [2:0]. since ich10 enclosure management does not support port multiplier based led message, the led message will be generated independ ently based on respective port?s operation activity. vendor specific led values locate (bits 5:3) and fault (bits 8:6) always are driven by software. 1 port multiplier information: specifies slot specific in formation related to port multiplier. bits 3:0 specify the port mult iplier port number for the sl ot that requires the status update. if a port multiplier is not attached to the device in the affected slot, the port multiplier port number shall be '0'. bits 7:4 are reserved. ich10 does not support led messages for device s behind a port multiplier . this byte should be 0. 0 hba information: specifies slot specific information related to the hba. bits 4:0 - hba port number for the sl ot that requires the status update. bit 5 - if set to '1', value is a vendor specific message that applies to the entire enclosure. if cleared to '0', value a pplies to the port specified in bits 4:0. bits 7:6 - reserved http://www..net/ datasheet pdf - http://www..net/ functional description 188 datasheet 5.16.12.4 sgpio waveform figure 5-12. serial data transm itted over the sgpio interface http://www..net/ datasheet pdf - http://www..net/ datasheet 189 functional description 5.16.13 external sata ich10 supports external sata. external sata utilizes the sata interface outside of the system box. the usage model for this feature must comply with the serial ata ii cables and connectors volume 2 gold specific ation at www.sata-io.org. intel validates two configurations: 1. the cable-up solution involves an internal sata cable that connects to the sata motherboard connector and spans to a back panel pci bracket with an e-sata connector. a separate e-sata cable is required to connect an e-sata device. 2. the back-panel solution involves running a trace to the i/o back panel and connecting a device via an external sata connector on the board. 5.17 high precision event timers this function provides a set of timers that can be used by the operating system. the timers are defined such that in the future, the operating system may be able to assign specific timers to used directly by specific applications. each timer can be configured to cause a separate interrupt. ich10 provides eight (corporate family) or four (consumer family) timers. the timers are implemented as a single counter each with its own comparator and value register. this counter increases monotonically. each individual timer can generate an interrupt when the value in its value register matches the value in the main counter. the registers associated with these timers are mapped to a memory space (much like the i/o apic). however, it is not implemen ted as a standard pci function. the bios reports to the operating system the location of the register space. the hardware can support an assignable decode space; however, the bios sets this space prior to handing it over to the operating system (see section 9.4 ). it is not expected that the operating system will move the location of these timers once it is set by the bios. 5.17.1 timer accuracy 1. the timers are accurate over any 1 ms peri od to within 0.05% of the time specified in the timer resolution fields. 2. within any 100 microsecond period, the timer reports a time that is up to two ticks too early or too late. each tick is less than or equal to 100 ns, so this represents an error of less than 0.2%. 3. the timer is monotonic. it does not return the same value on two consecutive reads (unless the counter has rolled over and reached the same value). the main counter is clocked by the 14.31818 mhz clock, synchronized into the 66.666 mhz domain. this results in a non-uniform du ty cycle on the synchronized clock, but does have the correct average period. the accuracy of the main counter is as accurate as the 14.31818 mhz clock. http://www..net/ datasheet pdf - http://www..net/ functional description 190 datasheet 5.17.2 interrupt mapping mapping option #1 (legacy replacement option) in this case, the legacy replacement rout bit (leg_rt_cnf) is set. this forces the mapping found in ta b l e 5 - 4 3 . note: (corporate only) the legacy option does not preclude delivery of irq0/irq8 via direct fsb interrupt messages. mapping option #2 (standard option) in this case, the legacy replacement rout bit (leg_rt_cnf) is 0. each timer has its own routing control. the interrupts can be routed to various interrupts in the 8259 or i/o apic. a capabilities field indicates which in terrupts are valid options for routing. if a timer is set for edge-triggered mode, the timers should not be share with any pci interrupts. for the intel ich10, the only suppor ted interrupt values are as follows: timer 0 and 1: irq20, 21, 22 & 23 (i/o apic only). timer 2: irq11 (8259 or i/o apic) and irq20, 21, 22, and 23 (i/o apic only). timer 3: irq12 (8259 or i/o apic) and irq 20, 21, 22, and 23 (i/o apic only). interrupts from timer 4, 5, 6, 7 (corporate only) can only be delivered via direct fsb interrupt messages. 5.17.3 periodic vs. no n-periodic modes non-periodic mode timer 0 is configurable to 32 (default) or 64-bit mode, whereas timers 1, 2 and 3 only support 32-bit mode (see section 21.1.5 ). all of the timers support non-periodic mode. consult section 2.3.9.2.1 of the ia-pc hpet specification for a description of this mode. periodic mode timer 0 is the only timer that supports periodic mode. consult section 2.3.9.2.2 of the ia-pc hpet specification for a description of this mode. table 5-43. legacy replacement routing timer 8259 mapping apic mapping comment 0irq0 irq2 in this case, the 8254 timer will not cause any interrupts 1irq8 irq8 in this case, the rtc will not cause any interrupts. 2 & 3 per irq routing fiel d. per irq routing field 4, 5, 6, 7 (corporate only) not available not available http://www..net/ datasheet pdf - http://www..net/ datasheet 191 functional description the following usage model is expected: 1. software clears the enable_cnf bit to prevent any interrupts 2. software clears the main counter by writing a value of 00h to it. 3. software sets the timer0_val_set_cnf bit. 4. software writes the new value in the timer0_comparator_val register 5. software sets the enable_cnf bit to enable interrupts. the timer 0 comparator value register cannot be programmed reliably by a single 64-bit write in a 32-bit environment except if only the periodic rate is being changed during run-time. if the actual timer 0 comparator value needs to be reinitialized, then the following software solution will always work regardless of the environment: 1. set timer0_val_set_cnf bit 2. set the lower 32 bits of the timer0 comparator value register 3. set timer0_val_set_cnf bit 4. set the upper 32 bits of the timer0 comparator value register 5.17.4 enabling the timers the bios or operating system pnp code shou ld route the interrupts. this includes the legacy rout bit, interrupt rout bit (for each timer), interrupt type (to select the edge or level type for each timer) the device driver code should do the following for an available timer: 1. set the overall enable bit (offset 10h, bit 0). 2. set the timer type field (selects one-shot or periodic). 3. set the interrupt enable 4. set the comparator value 5.17.5 interrupt levels interrupts directed to the internal 8259s are active high. see section 5.9 for information regarding the polarity programmin g of the i/o apic for detecting internal interrupts. if the interrupts are mapped to the 8259 or i/o apic and set for level-triggered mode, they can be shared with pci interrupts. they may be shared although it?s unlikely for the operating system to attempt to do this. if more than one timer is configured to share the same irq (using the timern_int_rout_cnf fields), then the software must configure the timers to level- triggered mode. edge-triggered interrupts cannot be shared. http://www..net/ datasheet pdf - http://www..net/ functional description 192 datasheet 5.17.6 handling interrupts if each timer has a unique interrupt and the timer has been configured for edge- triggered mode, then there are no specific steps required. no read is required to process the interrupt. if a timer has been configured to level-tr iggered mode, then its interrupt must be cleared by the software. this is done by reading the interrupt status register and writing a 1 back to the bit position for the interrupt to be cleared. independent of the mode, software can read the value in the main counter to see how time has passed between when the interrupt was generated and when it was first serviced. if timer 0 is set up to generate a periodic interrupt, the software can check to see how much time remains until the next interrupt by checking the timer value register. 5.17.7 issues related to 64-bit timers with 32-bit processors a 32-bit timer can be read directly using processors that are capable of 32-bit or 64-bit instructions. however, a 32-bit processor may not be able to directly read 64-bit timer. a race condition comes up if a 32-bit proc essor reads the 64-bit register using two separate 32-bit reads. the danger is that ju st after reading one half, the other half rolls over and changes the first half. if a 32-bit processor needs to access a 64-bit timer, it must first halt the timer before reading both the upper and lower 32-bits of the timer. if a 32-bit processor does not want to halt the timer, it can use the 64-bit timer as a 32-bit timer by setting the timern_32mode_cnf bit. this causes the time r to behave as a 32-bit timer. the upper 32-bits are always 0. alternatively, software may do a multiple read of the counter while it is running. software can read the high 32 bits, then the low 32 bits, the high 32 bits again. if the high 32 bits have not changed between the two reads, then a rollover has not happened and the low 32 bits are valid. if the high 32 bits have changed between reads, then the multiple reads are re peated until a valid read is performed. note: on a 64-bit platform, if software attempts a 64 bit read of the 64-bit counter, software must be aware that some platforms may split the 64 bit read into two 32 bit reads. the read maybe inaccurate if the low 32 bits roll over between the high and low reads. 5.18 usb uhci host controllers (d29:f0, f1, f2, f3 and d26:f0, f1 and f2) the ich10 contains six usb full/low-speed host controllers that support the standard universal host controller interface (uhci), revision 1.1. each uhci host controller (uhc) includes a root hub with two separate usb ports each, for a total of twelve usb ports. ? overcurrent detection on all twelve usb ports is supported. the overcurrent inputs are not 5 v tolerant, and can be used as gpis if not needed. ? the ich10?s uhci host controllers are ar bitrated differently than standard pci devices to improve arbitration latency. ? the uhci controllers use the analog fr ont end (afe) embedded cell that allows support for usb full-speed signaling rates, instead of usb i/o buffers. note: d26:f2 can be configured as d29:f3 during bios post. http://www..net/ datasheet pdf - http://www..net/ datasheet 193 functional description 5.18.1 data structur es in main memory section 3.1 - 3.3 of the universal host controller interface specification, revision 1.1 details the data structures used to communicate control, status, and data between software and the ich10. 5.18.2 data transfers to/from main memory section 3.4 of the universal host controller interface specification, revision 1.1 describes the details on how hcd and the ich10 communicate via the schedule data structures. 5.18.3 data encoding and bit stuffing the ich10 usb employs nrzi data encoding (non-return to zero inverted) when transmitting packets. full details on this implementation are given in the universal serial bus specification, revision 2.0 . 5.18.4 bus protocol 5.18.4.1 bit ordering bits are sent out onto the bus least significant bit (lsb) first, followed by next lsb, through to the most significant bit (msb) last. 5.18.4.2 sync field all packets begin with a synchronization (sync) field, which is a coded sequence that generates a maximum edge transition densit y. the sync field appears on the bus as idle followed by the binary string ?kjkjkjkk,? in its nrzi encoding. it is used by the input circuitry to align incoming data with the local clock and is defined to be 8 bits in length. sync serves only as a synchronizat ion mechanism. the last two bits in the sync field are a marker that is used to identify the first bit of the pid. all subsequent bits in the packet must be indexed from this point. 5.18.4.3 packet field formats all packets have distinct start and end of pa cket delimiters. full details are given in the universal serial bus specif ication, revision 2.0, in section 8.3.1. 5.18.4.4 address fields function endpoints are addressed using th e function address field and the endpoint field. full details on this are given in the universal serial bus specification, revision 2.0 , in section 8.3.2. 5.18.4.5 frame number field the frame number field is an 11-bit field that is incremented by the host on a per frame basis. the frame number field rolls over upon reaching its maximum value of 7ffh, and is sent only for sof tokens at the start of each frame. 5.18.4.6 data field the data field may range from 0 to 1023 by tes and must be an integral numbers of bytes. data bits within each byte are shifted out lsb first. http://www..net/ datasheet pdf - http://www..net/ functional description 194 datasheet 5.18.4.7 cyclic redundancy check (crc) crc is used to protect the all non-pid fields in token and data packets. in this context, these fields are considered to be protected fields. full details on this are given in the universal serial bus specification, revision 2.0 , in section 8.3.5. 5.18.5 packet formats the usb protocol calls out several packet types: token, data, and handshake packets. full details on this are given in the universal serial bus specification, revision 2.0 , in section 8.4. 5.18.6 usb interrupts there are two general groups of usb interrupt sources, those resulting from execution of transactions in the schedule, and those re sulting from an ich10 operation error. all transaction-based sources can be masked by software through the ich10?s interrupt enable register. additionally, individual tran sfer descriptors can be marked to generate an interrupt on completion. when the ich10 drives an interrupt for usb, it internally drives the pirqa# pin for usb function #0 and usb function #3, pirqd# pin for usb function #1, and the pirqc# pin for usb function #2, until all sources of the interrupt are cleared. in order to accommodate some operating systems, the interrupt pin register must contain a different value for each function of this new multi-function device. 5.18.6.1 transactio n-based interrupts these interrupts are not signaled until after the status for the last complete transaction in the frame has been written back to host memory. this ensures that software can safely process through (frame list current in dex -1) when it is servicing an interrupt. crc error / time-out a crc/time-out error occurs when a pack et transmitted from the ich10 to a usb device or a packet transmitted from a usb device to the ich10 generates a crc error. the ich10 is informed of this event by a time-out from the usb device or by the ich10?s crc checker generating an error on reception of the packet. additionally, a usb bus time-out occurs when usb devices do not respond to a transaction phase within 19-bit times of an eop. either of th ese conditions causes the c_err field of the td to decrement. when the c_err field decrements to 0, the following occurs: ? the active bit in the td is cleared ? the stalled bit in the td is set ? the crc/time-out bit in the td is set. ? at the end of the frame, the usb error interrupt bit is set in the hc status register. if the crc/time out interrupt is enabled in the interrupt enable register, a hardware interrupt will be signaled to the system. http://www..net/ datasheet pdf - http://www..net/ datasheet 195 functional description interrupt on completion transfer descriptors contain a bit that can be set to cause an interrupt on their completion. the completion of the transactio n associated with that block causes the usb interrupt bit in the hc status register to be set at the end of the frame in which the transfer completed. when a td is encount ered with the ioc bit set to 1, the ioc bit in the hc status register is set to 1 at the end of the frame if the active bit in the td is set to 0 (even if it was set to 0 when initially read). if the ioc enable bit of interrupt enable re gister (bit 2 of i/o offset 04h) is set, a hardware interrupt is signaled to the syst em. the usb interrupt bit in the hc status register is set either when the td complete s successfully or because of errors. if the completion is because of errors, the usb error bit in the hc status register is also set. short packet detect a transfer set is a collection of data which requires more than one usb transaction to completely move the data across the usb. an example might be a large print file which requires numerous tds in multiple frames to completely transfer the data. reception of a data packet that is less than the endpoint?s max packet size during control, bulk or interrupt transfers signals the completion of the transfer set, even if there are active tds remaining for this transfer set. setting the spd bit in a td indicates to the hc to set the usb interrupt bit in the hc status regi ster at the end of the frame in which this event occurs. this feature streamlines the proc essing of input on these transfer types. if the short packet interrupt enable bit in the interrupt enable register is set, a hardware interrupt is signaled to the syst em at the end of the frame where the event occurred. serial bus babble when a device transmits on the usb for a time greater than its assigned max length, it is said to be babbling. since isochrony can be destroyed by a babbling device, this error results in the active bit in the td being cl eared to 0 and the stalled and babble bits being set to 1. the c_err field is not decremented for a babble. the usb error interrupt bit in the hc status register is se t to 1 at the end of the frame. a hardware interrupt is signaled to the system. if an eof babble was caused by the ich10 (d ue to incorrect schedule for instance), the ich10 forces a bit stuff error followed by an eop and the start of the next frame. stalled this event indicates that a device/endpo int returned a stall handshake during a transaction or that the transaction ended in an error condition. the tds stalled bit is set and the active bit is cleared. reception of a stall does not decrement the error counter. a hardware interrupt is signaled to the system. data buffer error this event indicates that an overrun of inco ming data or a under-run of outgoing data has occurred for this transaction. this would generally be caused by the ich10 not being able to access required data buffers in memory within necessary latency requirements. either of these conditions causes the c_err field of the td to be decremented. when c_err decrements to 0, the active bit in the td is cleared, the stalled bit is set, the usb error interrupt bit in the hc status re gister is set to 1 at the end of the frame and a hardware interrupt is signaled to the system. http://www..net/ datasheet pdf - http://www..net/ functional description 196 datasheet bit stuff error a bit stuff error results from the detection of a sequence of more that six 1s in a row within the incoming data stream. this causes the c_err field of the td to be decremented. when the c_err field decrements to 0, the active bit in the td is cleared to 0, the stalled bit is set to 1, the usb erro r interrupt bit in the hc status register is set to 1 at the end of the frame and a hard ware interrupt is signaled to the system. 5.18.6.2 non-transaction based interrupts if an ich10 process error or system erro r occurs, the ich10 halts and immediately issues a hardware interrupt to the system. resume received this event indicates that the ich10 received a resume signal from a device on the usb bus during a global suspend. if this interrupt is enabled in the interrupt enable register, a hardware interrupt is signaled to the system allowing the usb to be brought out of the suspend state and returned to normal operation. ich10 process error the hc monitors certain critical fields during operation to ensure that it does not process corrupted data structures. these include checking for a valid pid and verifying that the maxlength field is less than 1280. if it detects a condition that would indicate that it is processing corrupted data structures, it immediately halts processing, sets the hc process error bit in the hc status register and signals a hardware interrupt to the system. this interrupt cannot be disabled through the interrupt enable register. host system error the ich10 sets this bit to 1 when a parity e rror, master abort, or target abort occurs. when this error occurs, the ich10 clears th e run/stop bit in the command register to prevent further execution of the scheduled tds. this interrupt cannot be disabled through the interrupt enable register. http://www..net/ datasheet pdf - http://www..net/ datasheet 197 functional description 5.18.7 usb power management the host controller can be put into a susp ended state and its power can be removed. this requires that certain bits of informatio n are retained in the suspend power plane of the ich10 so that a device on a port may wake the system. such a device may be a fax-modem, which will wake up the machine to receive a fax or take a voice message. the settings of the following bits in i/o spac e will be maintained when the ich10 enters the s3, s4, or s5 states. when the ich10 detects a resume event on an y of its ports, it sets the corresponding usb_sts bit in acpi space. if usb is en abled as a wake/break event, the system wakes up and an sci generated. 5.18.8 usb legacy keyboard operation when a usb keyboard is plugged into the sy stem, and a standard ke yboard is not, the system may not boot, and ms-dos legacy so ftware will not run, because the keyboard will not be identified. the ich10 implements a series of trapping operations which will snoop accesses that go to the keyboard controller, and put the expected data from the usb keyboard into the keyboard controller. note: the scheme described below assumes that the keyboard controller (8042 or equivalent) is on the lpc bus. this legacy operation is performed through smm space. figure 5-13 shows the enable and status path. the latched smi source (60r, 60w, 64r, 64w) is available in the status register. because the enable is after the latch, it is possible to check for other events that didn't necessarily cause an smi. it is the software's responsibility to logically and the value with the appropriate enable bits. note also that the smi is generated before the pci cycle completes (e.g., before trdy# goes active) to ensure that the processor do esn't complete the cycle before the smi is observed. the logic also needs to block the accesses to the 8042. if there is an external 8042, then this is simply accomplished by not activa ting the 8042 cs. this is done by logically anding the four enables (60r, 60w, 64r, 64w) with the 4 types of accesses to determine if 8042cs should go active. an ad ditional term is required for the ?pass- through? case. the state table for figure 5-13 is shown in ta b l e 5 - 4 5 . table 5-44. bits maintained in low power states register offset bit description command 00h 3 enter global suspend mode (egsm) status 02h 2 resume detect port status and control 10h & 12h 2 port enabled/disabled 6 resume detect 8 low-speed device attached 12 suspend http://www..net/ datasheet pdf - http://www..net/ functional description 198 datasheet figure 5-13. usb legacy keyboard flow diagram table 5-45. usb legacy keyboard state transitions (sheet 1 of 2) current state action data value next state comment idle 64h / write d1h gatestate1 standard d1 command. cycle passed through to 8042. smi# doesn't go active. pstate (offset c0, bit 6) goes to 1. idle 64h / write not d1h idle bit 3 in config register determines if cycle passed through to 8042 and if smi# generated. idle 64h / read n/a idle bit 2 in config register determines if cycle passed through to 8042 and if smi# generated. idle 60h / write don't care idle bit 1 in config register determines if cycle passed through to 8042 and if smi# generated. idle 60h / read n/a idle bit 0 in config register determines if cycle passed through to 8042 and if smi# generated. gatestate1 60h / write xxh gatestate2 cycle passed through to 8042, even if trap enabled in bit 1 in conf ig register. no smi# generated. pstate remains 1. if data value is not dfh or ddh then the 8042 may chose to ignore it. kbc accesses pci config read, write 60 read clear smi_60_r en_smi_on_60r comb. decoder and same for 60w, 64r, 64w smi or to individual "caused by" "bits" to pirqd# to "caused by" bit and and en_pirqd# usb_irq clear usb_irq en_smi_on_irq s d r s d r http://www..net/ datasheet pdf - http://www..net/ datasheet 199 functional description gatestate1 64h / write d1h gatestate1 cycle passed through to 8042, even if trap enabled via bit 3 in config register. no smi# generated. pstate remains 1. stay in gatestate1 because this is part of the double-trigge r sequence. gatestate1 64h / write not d1h ilde bit 3 in config space determines if cycle passed through to 8042 and if smi# generated. pstate goes to 0. if bit 7 in config register is set, then smi# should be generated. gatestate1 60h / read n/a idle this is an invalid sequence. bit 0 in config register determines if cycle passed through to 8042 and if smi# generated. pstate goes to 0. if bit 7 in config register is set, then smi# should be generated. gatestate1 64h / read n/a gatestate1 just stay in same state. generate an smi# if enabled in bit 2 of config register. pstate remains 1. gatestate2 64 / write ffh idle standard end of sequ ence. cycle passed through to 8042. pstate goes to 0. bit 7 in config space determines if smi# should be generated. gatestate2 64h / write not ffh idle improper end of sequence. bit 3 in config register determines if cycle passed through to 8042 and if smi# generated. pstate goes to 0. if bit 7 in config register is set, then smi# should be generated. gatestate2 64h / read n/a gatestate2 just stay in same state. generate an smi# if enabled in bit 2 of config register. pstate remains 1. gatestate2 60h / write xxh idle improper end of sequence. bit 1 in config register determines if cycle passed through to 8042 and if smi# generated. pstate goes to 0. if bit 7 in config register is set, then smi# should be generated. gatestate2 60h / read n/a idle improper end of sequence. bit 0 in config register determines if cycle passed through to 8042 and if smi# generated. pstate goes to 0. if bit 7 in config register is set, then smi# should be generated. table 5-45. usb legacy keyboard state transitions (sheet 2 of 2) current state action data value next state comment http://www..net/ datasheet pdf - http://www..net/ functional description 200 datasheet 5.18.9 function level reset support (flr) the usb uhci controllers support the function level reset (flr) capability. the flr capability can be used in conjunction with intel virtualization technology. flr allows an operating system in a virtual machine to have complete control over a device, including its initialization, without interferin g with the rest of the platform. the device provides a software interface that enables the operating system to reset the whole device as if a pci reset was asserted. 5.18.9.1 flr steps 5.18.9.1.1 flr initialization 1. a flr is initiated by software writing a 1 to the initiate flr bit. 2. all subsequent requests targeting the function will not be claimed and will be master abort immediate on the bus. this includes any configuration, i/o or memory cycles, however, the function shall continue to accept completions targeting the function. 5.18.9.1.2 flr operation the function will reset all configuration, i/o and memory registers of the function except those indicated otherwise and reset a ll internal states of the function to the default or initial condition. 5.18.9.1.3 flr completion the initiate flr bit is reset (cleared) when the flr reset is comple ted. this bit can be used to indicate to the software that the flr reset is completed. note: from the time initiate flr bit is written to 1, software must wait at least 100 ms before accessing the function. http://www..net/ datasheet pdf - http://www..net/ datasheet 201 functional description 5.19 usb ehci host contro llers (d29:f7 and d26:f7) the ich10 contains two enhanced host controller interface (ehci) host controllers which support up to twelve usb 2.0 high-speed root ports. usb 2.0 allows data transfers up to 480 mb/s using the same pins as the twelve usb full-speed/low-speed ports. the ich10 contains port-routing logic that determines whether a usb port is controlled by one of the uhci controllers or by one of the ehci controllers. usb 2.0 based debug port is also implemented in the ich10. a summary of the key architectural differences between the usb uhci host controllers and the ehci host controller are shown in ta b l e 5 - 4 6 . 5.19.1 ehc initialization the following descriptions step through the expected ich10 enhanced host controller (ehc) initialization sequence in chronologica l order, beginning with a complete power cycle in which the suspend well and core well have been off. 5.19.1.1 bios initialization bios performs a number of platform customization steps after the core well has powered up. contact your intel field representative for additional ich10 bios information. 5.19.1.2 driver initialization see chapter 4 of the enhanced host controller interface specification for universal serial bus, revision 1.0. table 5-46. uhci vs. ehci parameter usb uhci usb ehci accessible by i/o space memory space memory data structure single linked list separated into periodic and asynchronous lists differential signaling voltage 3.3 v 400 mv ports per controller 2 6 or 8 (controller #1) and 6 or 4 (controller #2) http://www..net/ datasheet pdf - http://www..net/ functional description 202 datasheet 5.19.1.3 ehc resets in addition to the standard ich10 hardware resets, portions of the ehc are reset by the hcreset bit and the transition from the d3 hot device power management state to the d0 state. the effects of each of these resets are: if the detailed register descriptions give exceptions to these rules, those exceptions override these rules. this summary is provid ed to help explain the reasons for the reset policies. 5.19.2 data structures in main memory see section 3 and appendix b of the enhanced host controller interface specification for universal serial bus, revision 1.0 for details. 5.19.3 usb 2.0 enhanced host controller dma the ich10 usb 2.0 ehc implements three sour ces of usb packets. they are, in order of priority on usb during each microframe: 1. the usb 2.0 debug port (see section usb 2.0 based debug port), 2. the periodic dma engine, and 3. the asynchronous dma engine. the ich10 always performs any currently-pending debug port transaction at the beginning of a microframe, followed by any pending periodic traffic for the current microframe. if there is time left in the mi croframe, then the ehc performs any pending asynchronous traffic until the end of the microframe (eof1). note that the debug port traffic is only presented on one port (port #0), while the other ports are idle during this time. 5.19.4 data encoding and bit stuffing see chapter 8 of the universal serial bus specification, revision 2.0. reset does reset does not reset comments hcreset bit set. memory space registers except structural parameters (which is written by bios). configuration registers. the hcreset must only affect registers that the ehci driver controls. pci configuration space and bios-programmed parameters can not be reset. software writes the device power state from d3 hot (11b) to d0 (00b). core well registers (except bios- programmed registers). suspend well registers; bios- programmed core well registers. the d3-to-d0 transition must not cause wake information (suspend well) to be lost. it also must not clear bios- programmed registers because bios may not be invoked following the d3-to-d0 transition. http://www..net/ datasheet pdf - http://www..net/ datasheet 203 functional description 5.19.5 packet formats see chapter 8 of the universal serial bus specification, revision 2.0 . the ich10 ehci allows entrance to usb test modes, as defined in the usb 2.0 specification, including test j, test packet, etc. however note that the ich10 test packet test mode interpacket gap timing may not meet the usb 2.0 specification. 5.19.6 usb 2.0 interrupts and error conditions section 4 of the enhanced host controller interface specification for universal serial bus, revision 1.0 goes into detail on the ehc interrupts and the error conditions that cause them. all error conditions that the ehc detects can be reported through the ehci interrupt status bits. only ich10-specific interrupt and error-reporting behavior is documented in this section. the ehci interrupts section must be read first, followed by this section of the datasheet to fully comp rehend the ehc interrupt and error-reporting functionality. ? based on the ehc?s buffer sizes and buffer management policies, the data buffer error can never occur on the ich10. ? master abort and target abort responses from hub interface on ehc-initiated read packets will be treated as fatal host erro rs. the ehc halts when these conditions are encountered. ? the ich10 may assert the interrupts whic h are based on the interrupt threshold as soon as the status for the last complete transaction in the interrupt interval has been posted in the internal writ e buffers. the requirement in the enhanced host controller interface specificatio n for universal serial bus, revision 1.0 (that the status is written to memory) is met internally, even though the write may not be seen on dmi before the interrupt is asserted. ? since the ich10 supports the 1024-elem ent frame list size, the frame list rollover interrupt occurs every 1024 milliseconds. ? the ich10 delivers interrupts using pirqh#. ? the ich10 does not modify the cerr count on an interrupt in when the ?do complete-split? execution criteria are not met. ? for complete-split transactions in the peri odic list, the ?missed microframe? bit does not get set on a control-structure-fetch that fails the late-start test. if subsequent accesses to that control structure do not fail the late-start test, then the ?missed microframe? bit will get set and written back. 5.19.6.1 aborts on usb 2. 0-initiated memory reads if a read initiated by the ehc is aborted, th e ehc treats it as a fatal host error. the following actions are taken when this occurs: ? the host system error status bit is set ? the dma engines are halted after completi ng up to one more transaction on the usb interface ? if enabled (by the host system error enable), then an interrupt is generated ? if the status is master abort, then the received master abort bit in configuration space is set ? if the status is target abort, then the received target abort bit in configuration space is set ? if enabled (by the serr enable bit in the function?s configuration space), then the signaled system error bit in configuration bit is set. http://www..net/ datasheet pdf - http://www..net/ functional description 204 datasheet 5.19.7 usb 2.0 power management 5.19.7.1 pause feature this feature allows platforms to dynamically enter low-power states during brief periods when the system is idle (i.e., betw een keystrokes). this is useful for enabling power management features in the ich10. the policies for entering these states typically are based on the recent history of system bus activity to incrementally enter deeper power management states. normally, when the ehc is enabled, it regularly accesses main memory while traversing the dma schedules looking for work to do; this activity is viewed by the power management software as a non-idle system, thus preventing the power managed states to be entered. suspending all of the enabled ports can prevent the memory accesses from occurring, but there is an inherent latency overhead with entering and exiting the suspended state on the usb ports that makes this unacceptable for the purpose of dynamic power management. as a result, the ehci software drivers are allowed to pause the ehc?s dma engines when it knows that the traffic patterns of the attached de vices can afford the delay. the pause only prevents the ehc from generating memory accesses; the sof packets continue to be generated on the usb ports (unlike the suspended state). 5.19.7.2 suspend feature the enhanced host controller interface (ehci) for universal serial bus specification , section 4.3 describes the details of port suspend and resume. 5.19.7.3 acpi device states the usb 2.0 function only supports the d0 and d3 pci power management states. notes regarding the ich10 implemen tation of the device states: 1. the ehc hardware does not inherently consume any more power when it is in the d0 state than it does in the d3 state. however, software is required to suspend or disable all ports prior to entering the d3 state such that the maximum power consumption is reduced. 2. in the d0 state, all implemented ehc features are enabled. 3. in the d3 state, accesses to the ehc me mory-mapped i/o range will master abort. note that, since the debug port uses the same memory range, the debug port is only operational when the ehc is in the d0 state. 4. in the d3 state, the ehc interrupt must never assert for any reason. the internal pme# signal is used to signal wake events, etc. 5. when the device power state field is wri tten to d0 from d3, an internal reset is generated. see section ehc resets for gene ral rules on the effects of this reset. 6. attempts to write any other value into the device power state field other than 00b (d0 state) and 11b (d3 state) will complete normally without changing the current value in this field. http://www..net/ datasheet pdf - http://www..net/ datasheet 205 functional description 5.19.7.4 acpi system states the ehc behavior as it relates to other power management states in the system is summarized in the following list: ? the system is always in the s0 state when the ehc is in the d0 state. however, when the ehc is in the d3 state, the system may be in any power management state (including s0). ? when in d0, the pause feature (see section 5.19.7.1 ) enables dynamic processor low-power states to be entered. ? the pll in the ehc is disabled when entering the s3/s4/s5 states (core power turns off). ? all core well logic is reset in the s3/s4/s5 states. 5.19.8 interaction with uhci host controllers the enhanced host controllers share its ports with uhci host controllers in the ich10. the uhc at d29:f0 shares ports 0 and 1; th e uhc at d29:f1 shares ports 2 and 3; the uhc at d29:f2 shares ports 4 and 5 with the ehc at d29:f7, while the uhc at d26:f0 shares ports 6 and 7, the uhc at d26:f1 shares ports 8 and 9, and the uhc at d26:f2 shares ports 10 and 11 with ehc at d26:f7. there is very little interaction between the enhanced and the uhci controllers other than the muxing control which is provided as part of the ehc. figure 5-14 shows the usb port connections at a conceptual level. note: d26:f2 can be configured as d29:f3 during bios post. http://www..net/ datasheet pdf - http://www..net/ functional description 206 datasheet 5.19.8.1 port-routing logic integrated into the ehc functionality is port -routing logic, which performs the muxing between the uhci and ehci host controllers. the ich10 conceptua lly implements this logic as described in section 4.2 of the enhanced host controller interface specification for universal serial bus, revision 1.0. if a device is connected that is not capable of usb 2.0?s high-speed signaling protocol or if the ehci software drivers are not present as indicated by the configured flag, then the uhci controller owns the port. owning the port means that the differential output is driven by the owner and the input stream is only visible to the owner. the host co ntroller that is not the owner of the port internally sees a disconnected port. note that the port-routing logic is the only block of logic within the ich10 that observes the physical (real) connect/disconnect information. the port status logic inside each of the host controllers observes the electrical connect/disconnect information that is generated by the port-routing logic. only the differential signal pairs are mult iplexed/de-multiplexed between the uhci and ehci host controllers. the other usb functional signals are handled as follows: ? the overcurrent inputs (oc[11:0]#) are directly routed to both controllers. an overcurrent event is recorded in both controllers? status registers. figure 5-14. intel ? ich10-usb port connections default six and six configuration figure 5-15. intel ? ich10-usb port connections eight and four configuration uhci uhci ehci #1 port 5 port 4 port 3 port 2 port 1 port 0 uhci uhci uhci uhci ehci #2 port 11 port 10 port 9 port 8 port 7 port 6 uhci uhci uhci uhci ehci #1 port 5 port 4 port 3 port 2 port 1 port 0 uhci uhci uhci uhci ehci #1 port 5 port 4 port 3 port 2 port 1 port 0 uhci uhci uhci uhci ehci #2 port 11 port 10 port 9 port 8 port 7 port 6 uhci uhci uhci uhci ehci #2 port 11 port 10 port 9 port 8 port 7 port 6 uhci uhci uhci uhci port 5 port 4 port 3 port 2 port 1 port 0 uhci uhci uhci uhci ehci #2 port 9 port 8 port 7 port 6 port 11 port 10 uhci uhci ehci #1 uhci uhci port 5 port 4 port 3 port 2 port 1 port 0 uhci uhci uhci uhci ehci #2 port 9 port 8 port 7 port 6 port 11 port 10 uhci uhci ehci #1 http://www..net/ datasheet pdf - http://www..net/ datasheet 207 functional description the port-routing logic is implemented in the suspend power well so that re- enumeration and re-mapping of the usb port s is not required following entering and exiting a system sleep state in which the core power is turned off. the ich10 also allows the usb debug port traffi c to be routed in and out of port #0 and port #6. when in this mode, the enhanced host controller is the owner of port #0 and port #6. 5.19.8.2 device connects the enhanced host controller interface specification for universal serial bus, revision 1.0 describes the details of handling device connects in section 4.2. there are four general scenarios that are summarized below. 1. configure flag = 0 and a full-speed/low-speed-only device is connected ? in this case, the uhc is the owner of th e port both before and after the connect occurs. the ehc (except for the port-routing logic) never sees the connect occur. the uhci driver handles the connection and initialization process. 2. configure flag = 0 and a high-speed-capable device is connected ? in this case, the uhc is the owner of th e port both before and after the connect occurs. the ehc (except for the port-routing logic) never sees the connect occur. the uhci driver handles the conne ction and initialization process. since the uhc does not perform the high-speed chirp handshake, the device operates in compatible mode. 3. configure flag = 1 and a full-speed/low-speed-only device is connected ? in this case, the ehc is the owner of the port before the connect occurs. the ehci driver handles the connection and pe rforms the port reset. after the reset process completes, the ehc hardware has cleared (not set) the port enable bit in the ehc?s portsc register. the ehci dr iver then writes a 1 to the port owner bit in the same register, causing the uh c to see a connect event and the ehc to see an ?electrical? disconnect event. the uhci driver and hardware handle the connection and initialization process from that point on. the ehci driver and hardware handle the perceived disconnect. 4. configure flag = 1 and a high-speed-capable device is connected ? in this case, the ehc is the owner of the port before, and remains the owner after, the connect occurs. the ehci driver handles the connection and performs the port reset. after the reset process completes, the ehc hardware has set the port enable bit in the ehc?s portsc register . the port is functional at this point. the uhc continues to see an unconnected port. http://www..net/ datasheet pdf - http://www..net/ functional description 208 datasheet 5.19.8.3 device disconnects the enhanced host controller interface spec ification for universal serial bus, revision 1.0 describes the details of handling device connects in section 4.2. there are three general scenarios that are summarized below. 1. configure flag = 0 and the device is disconnected ? in this case, the uhc is the owner of the port both before and after the disconnect occurs. the ehc (except for the port-routing logic) never sees a device attached. the uhci driver handles disconnection process. 2. configure flag = 1 and a full-speed/low-speed-capable device is disconnected ? in this case, the uhc is the owner of th e port before the disconnect occurs. the disconnect is reported by the uhc and serviced by the associated uhci driver. the port-routing logic in the ehc cluster forces the port owner bit to 0, indicating that the ehc owns the unconnected port. 3. configure flag = 1 and a high-sp eed-capable device is disconnected ? in this case, the ehc is the owner of the port before, and remains the owner after, the disconnect occurs. the ehci hardware and driver handle the disconnection process. the uhc never sees a device attached. 5.19.8.4 effect of resets on port-routing logic as mentioned above, the port routing logic is implemented in the suspend power well so that remuneration and re-mapping of the usb ports is not required following entering and exiting a system sleep state in which the core power is turned off. 5.19.9 usb 2.0 legacy keyboard operation the ich10 must support the possibility of a keyboard downstream from either a full- speed/low-speed or a high-speed port. the description of the legacy keyboard support is unchanged from usb 1.1 (see section 5.18.8 ). the ehc provides the basic ability to generate smis on an interrupt event, along with more sophisticated control of the generation of smis. reset event effect on configure flag effect on port owner bits suspend well reset cleared (0) set (1) core well reset no effect no effect d3-to-d0 reset no effect no effect hcreset cleared (0) set (1) http://www..net/ datasheet pdf - http://www..net/ datasheet 209 functional description 5.19.10 usb 2.0 based debug port the ich10 supports the elimination of the le gacy com ports by providing the ability for new debugger software to interact with devices on a usb 2.0 port. high-level restrictions and features are: ? operational before usb 2.0 drivers are loaded. ? functions even when the port is disabled. ? works even though non-configured port is default-routed to the uhci. note that the debug port can not be used to debug an issue that requires a full-speed/low- speed device on port #0 using the uhci drivers. ? allows normal system usb 2.0 traffic in a system that may only have one usb port. ? debug port device (dpd) must be high-speed capable and connect directly to port #0 and port #6 on ich10 systems (e.g., the dpd cannot be connected to port #0/port #6 through a hub). ? debug port fifo always makes forward progress (a bad status on usb is simply presented back to software). ? the debug port fifo is only given one usb access per microframe. the debug port facilitates operating system and device driver debug. it allows the software to communicate with an external console using a usb 2.0 connection. because the interface to this link does not go through the normal usb 2.0 stack, it allows communication with the external console during cases where the operating system is not loaded, the usb 2.0 software is broken, or where the usb 2.0 software is being debugged. specific features of th is implementation of a debug port are: ? only works with an external usb 2.0 debug device (console) ? implemented for a specific port on the host controller ? operational anytime the port is not susp ended and the host controller is in d0 power state. ? capability is interrupted when port is driving usb reset 5.19.10.1 theory of operation there are two operational modes for the usb debug port: 1. mode 1 is when the usb port is in a disa bled state from the viewpoint of a standard host controller driver. in mode 1, the debug port controller is required to generate a ?keepalive? packets less than 2 ms apart to keep the attached debug device from suspending. the keepalive packet should be a standalone 32-bit sync field. 2. mode 2 is when the host controller is running (i.e., host controller?s run/stop# bit is 1). in mode 2, the normal transmission of sof packets will keep the debug device from suspending. behavioral rules 1. in both modes 1 and 2, the debug port controller must check for software requested debug transactions at least every 125 microseconds. 2. if the debug port is enabled by the debug driver, and the standard host controller driver resets the usb port, usb debug transactions are held off for the duration of the reset and until after the first sof is sent. 3. if the standard host controller driver suspends the usb port, then usb debug transactions are held off for the duration of the suspend/resume sequence and until after the first sof is sent. 4. the enabled_cnt bit in the debug register space is independent of the similar port control bit in the associated port status and control register. http://www..net/ datasheet pdf - http://www..net/ functional description 210 datasheet ta b l e 5 - 4 7 shows the debug port behavior relate d to the state of bits in the debug registers as well as bits in the associated port status and control register. 5.19.10.1.1 out transactions an out transaction sends data to the debug device. it can occur only when the following are true: ? the debug port is enabled ? the debug software sets the go_cnt bit ? the write_read#_cnt bit is set the sequence of the transaction is: 1. software sets the appropriate values in the following bits: ? usb_address_cnf ?usb_endpoint_cnf ? data_buffer[63:0] ? token_pid_cnt[7:0] ?send_pid_cnt[15:8] ?data_len_cnt ? write_read#_cnt: (note: this will always be 1 for out transactions) ? go_cnt: (note: this will always be 1 to initiate the transaction) table 5-47. debug port behavior owner_cnt enabled_ct port enable run / stop suspend debug port behavior 0xxxx debug port is not being used. normal operation. 10xxx debug port is not being used. normal operation. 1100x debug port in mode 1. sync keepalives sent plus debug traffic 1101x debug port in mode 2. sof (and only sof) is sent as keepalive. debug traffic is also sent. note that no other normal traffic is sent out this port, because the port is not enabled. 11100 invalid. host controller driver should never put controller into this state (enabled, not running and not suspended). 11101 port is suspended. no debug traffic sent. 11110 debug port in mode 2. debug traffic is interspersed with normal traffic. 11111 port is suspended. no debug traffic sent. http://www..net/ datasheet pdf - http://www..net/ datasheet 211 functional description 2. the debug port controller sends a token packet consisting of: ?sync ? token_pid_cnt field ? usb_address_cnt field ?usb_endpoint_cnt field ? 5-bit crc field 3. after sending the token packet, the debug port controller sends a data packet consisting of: ?sync ? send_pid_cnt field ? the number of data bytes indicated in data_len_cnt from the data_buffer ? 16-bit crc note: ?a data_len_cnt value of 0 is valid in which case no data bytes would be included in the packet. 4. after sending the data packet, the controller waits for a handshake response from the debug device. ? if a handshake is received, the debug port controller: ? a. places the received pid in the received_pid_sts field ? b. resets the error_good#_sts bit ? c. sets the done_sts bit ? if no handshake pid is received, the debug port controller: ? a. sets the exception_sts field to 001b ? b. sets the error_good#_sts bit ? c. sets the done_sts bit 5.19.10.1.2 in transactions an in transaction receives data from the debug device. it can occur only when the following are true: ? the debug port is enabled ? the debug software sets the go_cnt bit ? the write_read#_cnt bit is reset the sequence of the transaction is: 1. software sets the appropriate values in the following bits: ?usb_address_cnf ?usb_endpoint_cnf ? token_pid_cnt[7:0] ?data_len_cnt ? write_read#_cnt: (note: this will always be 0 for in transactions.) ? go_cnt: (note: this will always be 1 to initiate the transaction.) http://www..net/ datasheet pdf - http://www..net/ functional description 212 datasheet 2. the debug port controller sends a token packet consisting of: ?sync ? token_pid_cnt field ? usb_address_cnt field ? usb_endpoint_cnt field ? 5-bit crc field. 3. after sending the token packet, the debug port controller waits for a response from the debug device. if a response is received: ? the received pid is placed into the received_pid_sts field ? any subsequent bytes are placed into the data_buffer ? the data_len_cnt field is updated to show the number of bytes that were received after the pid. 4. if a valid packet was received from th e device that was on e byte in length (indicating it was a handshake packet), then the debug port controller: ? resets the error_good#_sts bit ? sets the done_sts bit 5. if a valid packet was received from the device that was more than one byte in length (indicating it was a data pack et), then the debug port controller: ? transmits an ack handshake packet ? resets the error_good#_sts bit ? sets the done_sts bit 6. if no valid packet is received, then the debug port controller: ? sets the exception_sts field to 001b ? sets the error_good#_sts bit ? sets the done_sts bit. 5.19.10.1.3 debug software enabling the debug port there are two mutually exclusive conditions that debug software must address as part of its startup processing: ? the ehci has been initialized by system software ? the ehci has not been initialized by system software debug software can determine the current ?ini tialized? state of the ehci by examining the configure flag in the ehci usb 2.0 command register. if this flag is set, then system software has initialized the ehci. ot herwise the ehci should not be considered initialized. debug software will initialize th e debug port registers depending on the state of the ehci. however, before this can be accomplished, debug software must determine which root usb port is designated as the debug port. determining the debug port debug software can easily determine which usb root port has been designated as the debug port by examining bits 20:23 of the ehci host controller structural parameters register. this 4-bit field represents the numeric value assigned to the debug port (i.e., 0000 = port 0). http://www..net/ datasheet pdf - http://www..net/ datasheet 213 functional description debug software startup with non-initialized ehci debug software can attempt to use the debug port if after setting the owner_cnt bit, the current connect status bit in the ap propriate (see determining the debug port) portsc register is set. if the current co nnect status bit is not set, then debug software may choose to terminate or it may choose to wait until a device is connected. if a device is connected to the port, then debug software must reset/enable the port. debug software does this by setting and then clearing the port reset bit the portsc register. to ensure a successful reset, debug software should wait at least 50 ms before clearing the port reset bit. due to possible delays, this bit may not change to 0 immediately; reset is complete when this bi t reads as 0. software must not continue until this bit reads 0. if a high-speed device is attached, the eh ci will automatically set the port enabled/ disabled bit in the portsc register and the debug software can proceed. debug software should set the enabled_cnt bit in the debug port control/status register, and then reset (clear) the port enabled/disabl ed bit in the portsc register (so that the system host controller driver does not see an enabled port when it is first loaded). debug software startup with initialized ehci debug software can attempt to use the debug port if the current connect status bit in the appropriate (see determining the debug port) portsc register is set. if the current connect status bit is not set, then debug software may choose to terminate or it may choose to wait until a device is connected. if a device is connected, then debug software must set the owner_cnt bit and then the enabled_cnt bit in the debug port control/status register. determining debug peripheral presence after enabling the debug port functionality, debug software can determine if a debug peripheral is attached by attempting to send data to the debug peripheral. if all attempts result in an error (exception bits in the debug port control/status register indicates a transaction error), then the attached device is not a debug peripheral. if the debug port peripheral is not present, then debug software may choose to terminate or it may choose to wait until a debug peripheral is connected. 5.19.11 usb pre-fetch based pause the pre-fetch based pause is a power management feature in usb (ehci) host controllers to ensure maximum c3/c4 processo r power state time with c2 popup. this feature applies to the period schedule, and works by allowing the dma engine to identify periods of idleness and preventing the dma engine from accessing memory when the periodic schedule is idle. typically in the presence of periodic devices with multiple millisecond poll periods, the periodic schedule will be idle for several frames between polls. the usb pre-fetch based pause feature is disabled by setting bit 4 of ehci configuration register section 17.1.30 . http://www..net/ datasheet pdf - http://www..net/ functional description 214 datasheet 5.19.12 function level reset support (flr) the usb ehci controllers support the functi on level reset (flr) capability. the flr capability can be used in conjunction with intel virtualization technology. flr allows an operating system in a virtual machine to have complete control over a device, including its initialization, without interferin g with the rest of the platform. the device provides a software interface that enables the operating system to reset the whole device as if a pci reset was asserted. 5.19.12.1 flr steps 5.19.12.1.1 flr initialization 1. a flr is initiated by software writing a ?1? to the initiate flr bit. 2. all subsequent requests targeting the function will not be claimed and will be master abort immediate on the bus. this includes any configuration, i/o or memory cycles, however, the function shall continue to accept completions targeting the function. 5.19.12.1.2 flr operation the function will reset all configuration, i/o and memory registers of the function except those indicated otherwise and reset a ll internal states of the function to the default or initial condition. 5.19.12.1.3 flr completion the initiate flr bit is reset (cleared) when the flr reset is comple ted. this bit can be used to indicate to the software that the flr reset is completed. note: from the time initiate flr bit is written to 1, software must wait at least 100 ms before accessing the function. 5.20 smbus controller (d31:f3) the ich10 provides an system management bus (smbus) 2.0 host controller as well as an smbus slave interface. the host contro ller provides a mechanism for the processor to initiate communications with smbus periph erals (slaves). the ich10 is also capable of operating in a mode in which it can communicate with i 2 c compatible devices. the ich10 can perform smbus messages with either packet error checking (pec) enabled or disabled. the actual pec calculat ion and checking is performed in hardware by the ich10. the slave interface allows an external master to read from or write to the ich10. write cycles can be used to cause certain events or pass messages, and the read cycles can be used to determine the state of variou s status bits. the ich10?s internal host controller cannot access the ich10?s internal slave interface. the ich10 smbus logic exists in device 31:function 3 configuration space, and consists of a transmit data path, and host controller. the transmit data path provides the data flow logic needed to implement the seven different smbus command protocols and is controlled by the host controller. the ich10 smbus controller logic is clocked by rtc clock. the smbus address resolution protocol (arp) is supported by using the existing host controller commands through software, ex cept for the new host notify command (which is actually a received message). http://www..net/ datasheet pdf - http://www..net/ datasheet 215 functional description the programming model of the host controlle r is combined into two portions: a pci configuration portion, and a system i/o mapped portion. all static configuration, such as the i/o base address, is done via the pci configuration space. real-time programming of the host interface is done in system i/o space. the ich10 smbus host controller checks for pa rity errors as a target. if an error is detected, the detected parity error bit in the pci status register (device 31:function 3:offset 06h:bit 15) is set. if bit 6 and bit 8 of the pci command register (device 31:function 3:offset 04h) are set, an serr# is generated and the signaled serr# bit in the pci status register (bit 14) is set. 5.20.1 host controller the smbus host controller is used to send commands to other smbus slave devices. software sets up the host controller with an address, command, and, for writes, data and optional pec; and then tells the controlle r to start. when the controller has finished transmitting data on writes, or receiving data on reads, it generates an smi# or interrupt, if enabled. the host controller supports 8 command protocols of the smbus interface (see system management bus (smbus) specification, version 2.0 ): quick command, send byte, receive byte, write byte/word, read byte/word, process call, block read/write, block write?block read process call, and host notify. the smbus host controller requires that the various data and command fields be setup for the type of command to be sent. when so ftware sets the start bit, the smbus host controller performs the requested transa ction, and interrupts the processor (or generates an smi#) when the transaction is completed. once a start command has been issued, the values of the ?active re gisters? (host control, host command, transmit slave address, data 0, data 1) should not be changed or read until the interrupt status bit (intr) has been set (i ndicating the completion of the command). any register values needed for computation purposes should be saved prior to issuing of a new command, as the smbus host contro ller updates all registers while completing the new command. the ich10 supports the system management bus (smbus) specification, version 2.0 . slave functionality, including the host notify protocol, is available on the smbus pins. the smlink and smbus signals can be tied to gether externally depending on tco mode used. refer to section 5.14.2 for more details. using the smb host controller to send comma nds to the ich10?s smb slave port is not supported. 5.20.1.1 command protocols in all of the following commands, the host status register (offset 00h) is used to determine the progress of the command. wh ile the command is in operation, the host_busy bit is set. if th e command completes successfully, the intr bit will be set in the host status register. if the device does not respond with an acknowledge, and the transaction times out, the dev_err bit is set. if software sets the kill bit in the host control register while the command is running, the transaction will stop and the failed bit will be set. quick command when programmed for a quick command, the transmit slave address register is sent. the pec byte is never appended to the quick protocol. software should force the pec_en bit to 0 when performing the quick command. software must force the i2c_en bit to 0 when running this command. see section 5.5.1 of the system management bus (smbus) specification, version 2.0 for the format of the protocol. http://www..net/ datasheet pdf - http://www..net/ functional description 216 datasheet send byte / receive byte for the send byte command, the transmit slave address and device command registers are sent. for the receive byte command, the transmit slave address register is sent. the data received is stored in the data0 register. so ftware must force the i2c_en bit to 0 when running this command. the receive byte is similar to a send byte, the only difference is the direction of data transfer. see sections 5.5.2 and 5.5.3 of the system management bus (smbus) specification, version 2.0 for the format of the protocol. write byte/word the first byte of a write byte/word access is the command code. the next 1 or 2 bytes are the data to be written. when programmed for a write byte/word command, the transmit slave address, device command, and data0 registers are sent. in addition, the data1 register is sent on a write word command. software must force the i2c_en bit to 0 when running this comm and. see section 5.5.4 of the system management bus (smbus) specification, version 2.0 for the format of the protocol. read byte/word reading data is slightly more complicated than writing data. first the ich10 must write a command to the slave device. then it mu st follow that command with a repeated start condition to denote a read from that device's address. the slave then returns 1 or 2 bytes of data. software must force the i2c_en bit to 0 when running this command. when programmed for the read byte/word command, the transmit slave address and device command registers are sent. data is received into the data0 on the read byte, and the dat0 and data1 registers on th e read word. see section 5.5.5 of the system management bus (smbus) specification, version 2.0 for the format of the protocol. process call the process call is so named because a command sends data and waits for the slave to return a value dependent on that data. the protocol is simply a write word followed by a read word, but without a second command or stop condition. when programmed for the process call comm and, the ich10 transmits the transmit slave address, host command, data0 and data1 registers. data received from the device is stored in the data0 and data1 registers. the process call command with i2c_en set and the pec_en bit set produces undefined results. software must force either i2c_en or pec_en to 0 when running this command. see section 5.5.6 of the system management bus (smbus) specification, version 2.0 for the format of the protocol. note: for process call command, the value written into bit 0 of the transmit slave address register (smb i/o register, offset 04h) needs to be 0. note: if the i2c_en bit is set, the protocol se quence changes slightly: the command code (bits 18:11 in the bit sequence) are not sent - as a result, the slave will not acknowledge (bit 19 in the sequence). http://www..net/ datasheet pdf - http://www..net/ datasheet 217 functional description block read/write the ich10 contains a 32-byte buffer for read and write data which can be enabled by setting bit 1 of the auxiliary control register at offset 0dh in i/o space, as opposed to a single byte of buffering. this 32-byte buffer is filled with write data before transmission, and filled with re ad data on reception. in the ich10, the interrupt is generated only after a transmission or recept ion of 32 bytes, or when the entire byte count has been transmitted/received. the byte count field is transmitted but igno red by the ich10 as software will end the transfer after all bytes it cares about have been sent or received. for a block write, software must either force the i2c_en bit or both the pec_en and aac bits to 0 when running this command. the block write begins with a slave addre ss and a write condition. after the command code the ich10 issues a byte count describ ing how many more bytes will follow in the message. if a slave had 20 bytes to send, th e first byte would be the number 20 (14h), followed by 20 bytes of data. the byte count may not be 0. a block read or write is allowed to transfer a maximum of 32 data bytes. when programmed for a block write command, the transmit slave address, device command, and data0 (count) registers are sent. data is then sent from the block data byte register; the total data sent being the value stored in the data0 register. on block read commands, the first byte received is stored in the data0 register, and the remaining bytes are stored in the block data byte register. see section 5.5.7 of the system management bus (smbus) specification, version 2.0 for the format of the protocol. note: for block write, if the i2c_en bit is set, the format of the command changes slightly. the ich10 will still send the number of byte s (on writes) or receive the number of bytes (on reads) indicated in the data0 regist er. however, it will not send the contents of the data0 register as part of the message. also, the block write protocol sequence changes slightly: the byte count (bits 27:20 in the bit sequence) are not sent - as a result, the slave will not acknowledge (bit 28 in the sequence). http://www..net/ datasheet pdf - http://www..net/ functional description 218 datasheet i 2 c read this command allows the ich10 to perform block reads to certain i 2 c devices, such as serial e 2 proms. the smbus block read supports the 7-bit addressing mode only. however, this does not allow access to devices using the i 2 c ?combined format? that has data bytes after the address. typically these data bytes correspond to an offset (address) within the serial memory chips. note: this command is supported independent of the setting of the i2c_en bit. the i 2 c read command with the pec_en bit set produces undefined results. software must force both the pec_en and aac bit to 0 when running this command. for i 2 c read command, the value written into bit 0 of the transmit slave address register (smb i/o register, offset 04h) needs to be 0. the format that is used for the command is shown in ta b l e 5 - 4 8 . the ich10 will continue reading data from the peripheral until the nak is received. table 5-48. i 2 c block read bit description 1start 8:2 slave address ? 7 bits 9write 10 acknowledge from slave 18:11 send data1 register 19 acknowledge from slave 20 repeated start 27:21 slave address ? 7 bits 28 read 29 acknowledge from slave 37:30 data byte 1 from slave ? 8 bits 38 acknowledge 46:39 data byte 2 from slave ? 8 bits 47 acknowledge ? data bytes from slave / acknowledge ? data byte n from slave ? 8 bits ? not acknowledge ?stop http://www..net/ datasheet pdf - http://www..net/ datasheet 219 functional description block write?block read process call the block write-block read process call is a two-part message. the call begins with a slave address and a write condition. after the command code the host issues a write byte count (m) that describes how many more bytes will be written in the first part of the message. if a master has 6 bytes to send, the byte count field will have the value 6 (0000 0110b), followed by the 6 bytes of data. the write byte count (m) cannot be 0. the second part of the message is a block of read data beginning with a repeated start condition followed by the slave address and a re ad bit. the next byte is the read byte count (n), which may differ from the write byte count (m). the read byte count (n) cannot be 0. the combined data payload must not exceed 32 bytes. the byte leng th restrictions of this process call are summarized as follows: ?m 1 byte ?n 1 byte ?m + n 32 bytes the read byte count does not include the pe c byte. the pec is computed on the total message beginning with the first slav e address and using the normal pec computational rules. it is highly recommende d that a pec byte be used with the block write-block read process call. software mu st do a read to the command register (offset 2h) to reset the 32 byte buffer pointe r prior to reading the block data register. note that there is no stop condition before the repeated start condition, and that a nack signifies the end of the read transfer. note: e32b bit in the auxiliary control register must be set when using this protocol. see section 5.5.8 of the system management bus (smbus) specification, version 2.0 for the format of the protocol. 5.20.2 bus arbitration several masters may attempt to get on the bus at the same time by driving the smbdata line low to signal a start conditio n. the ich10 continuously monitors the smbdata line. when the ich10 is attempting to drive the bus to a 1 by letting go of the smbdata line, and it samp les smbdata low, then some other master is driving the bus and the ich10 will stop transferring data. if the ich10 sees that it has lost arbitration, the condition is called a collision. the ich10 will set the bus_err bit in the host stat us register, and if enabled, generate an interrupt or smi#. the processor is responsible for restarting the transaction. when the ich10 is a smbus master, it driv es the clock. when the ich10 is sending address or command as an smbus master, or data bytes as a master on writes, it drives data relative to the clock it is also driving. it will not start toggling the clock until the start or stop condition meets proper setup and hold time. the ich10 will also ensure minimum time between smbus transactions as a master. note: the ich10 supports the same arbitration pr otocol for both the smbus and the system management (smlink) interfaces. http://www..net/ datasheet pdf - http://www..net/ functional description 220 datasheet 5.20.3 bus timing 5.20.3.1 clock stretching some devices may not be able to handle their clock toggling at the rate that the ich10 as an smbus master would like. they have the capability of stretching the low time of the clock. when the ich10 attempts to release the clock (allowing the clock to go high), the clock will remain low for an extended period of time. the ich10 monitors the smbus clock line after it releases the bus to determine whether to enable the counter for the high time of the clock. while the bus is still low, the high time counter must not be enabled. simila rly, the low period of the clock can be stretched by an smbus master if it is not ready to send or receive data. 5.20.3.2 bus time out (intel ? ich10 as smbus master) if there is an error in the transaction, such that an smbus device does not signal an acknowledge, or holds the clock lower than the allowed time-out time, the transaction will time out. the ich10 will discard the cy cle and set the dev_err bit. the time out minimum is 25 ms (800 rtc clocks). the time-out counter inside the ich10 will start after the last bit of data is transferred by the ich10 and it is waiting for a response. the 25 ms timeout counter will not co unt under the following conditions: 1. byte_done_status bit (smbus i/o offset 00h, bit 7) is set 2. the second_to_sts bit (tco i/o offset 06h, bit 1) is not set (this indicates that the system has not locked up). http://www..net/ datasheet pdf - http://www..net/ datasheet 221 functional description 5.20.4 interrupts / smi# the ich10 smbus controller uses pirqb# as it s interrupt pin. however, the system can alternatively be set up to generate smi# instead of an interrupt, by setting the smbus_smi_en bit (device 31:function 0:offset 40h:bit 1). ta b l e 5 - 5 0 and ta b l e 5 - 5 1 specify how the various enable bits in the smbus function control the generation of the interrupt, host and slave smi, and wake internal signals. the rows in the tables are additive, which mean s that if more than one row is true for a particular scenario then the results for all of the activated rows will occur. table 5-49. enable for smbalert# event intren (host control i/o register, offset 02h, bit 0) smb_smi_en (host configuration register, d31:f3:offset 40h, bit 1) smbalert_dis (slave command i/o register, offset 11h, bit 2) result smbalert# asserted low (always reported in host status register, bit 5) xx xwake generated x1 0 slave smi# generated (smbus_smi_sts) 1 0 0 interrupt generated table 5-50. enables for smbus slave write and smbus host events event intren (host control i/o register, offset 02h, bit 0) smb_smi_en (host configuration register, d31:f3:offset 40h, bit1) event slave write to wake/ smi# command xx wake generated when asleep. slave smi# generated when awake (smbus_smi_sts). slave write to smlink_slave_smi command xx slave smi# generated when in the s0 state (smbus_smi_sts) any combination of host status register [4:1] asserted 0xnone 1 0 interrupt generated 11host smi# generated table 5-51. enables for the host notify command host_notify_intren (slave control i/o register, offset 11h, bit 0) smb_smi_en (host config register, d31:f3:off40h, bit 1) host_notify_wken (slave control i/o register, offset 11h, bit 1) result 0x0none xx1wake generated 1 0 x interrupt generated 11x slave smi# generated (smbus_smi_sts) http://www..net/ datasheet pdf - http://www..net/ functional description 222 datasheet 5.20.5 smbalert# smbalert# is multiplexed with gpio[11]. when enable and the signal is asserted, the ich10 can generate an interrupt, an smi#, or a wake event from s1?s5. 5.20.6 smbus crc gene ration and checking if the aac bit is set in the auxiliary contro l register, the ich10 automatically calculates and drives crc at the end of the transmitte d packet for write cycles, and will check the crc for read cycles. it will not transmit the contents of the pec register for crc. the pec bit must not be set in the host control re gister if this bit is set, or unspecified behavior will result. if the read cycle results in a crc error, the dev_err bit and the crce bit in the auxiliary status register at offset 0ch will be set. 5.20.7 smbus slave interface the ich10?s smbus slave interface is acce ssed via the smbus. the smbus slave logic will not generate or handle re ceiving the pec byte and will only act as a legacy alerting protocol device. the slave interface allows the ich10 to decode cycles, and allows an external microcontroller to perform specif ic actions. key features and capabilities include: ? supports decode of three types of messages: byte write, byte read, and host notify. ? receive slave address register: this is the address that the ich10 decodes. a default value is provided so that the slave interface can be used without the processor having to program this register. ? receive slave data register in the smbus i/o space that includes the data written by the external microcontroller. ? registers that the external microcontrolle r can read to get the state of the ich10. ? status bits to indicate that the smbus sl ave logic caused an interrupt or smi# due to the reception of a message that matched the slave address. ? bit 0 of the slave status register for the host notify command ? bit 16 of the smi status register ( section 13.8.3.13 ) for all others note: the external microcontroller should not attempt to access the intel ich10?s smbus slave logic until either: ? 800 milliseconds after both: rtcrst# is high and rsmrst# is high, or ? the pltrst# deasserts if a master leaves the clock and data bits of the smbus interface at 1 for 50 s or more in the middle of a cycle, the ich10 slave logic's behavior is undefined. this is interpreted as an unexpected idle an d should be avoided when performing management activities to the slave logic. note: when an external microcontroller accesses the smbus slave interface over the smbus a translation in the address is needed to accommodate the least significant bit used for read/write control. for example, if the ich10 slave address (rcv_slva) is left at 44h (default), the external micro controller woul d use an address of 88h/89h (write/read). http://www..net/ datasheet pdf - http://www..net/ datasheet 223 functional description 5.20.7.1 format of slave write cycle the external master performs byte write co mmands to the ich10 smbus slave i/f. the ?command? field (bits 11:18) indicate which register is being accessed. the data field (bits 20:27) indicate the value that should be written to that register. ta b l e 5 - 5 2 has the values associated with the registers. note: the external microcontroller is responsible to make sure th at it does not update the contents of the data byte registers until they have been read by the system processor. the ich10 overwrites the old value with any new value received. a race condition is possible where the new value is being written to the regist er just at the time it is being read. ich10 will not attempt to cover this race condition (i.e., unpredictable results in this case). . table 5-52. slave write registers register function 0 command register. see ta b l e 5 - 5 3 below for legal values written to this register. 1?3 reserved 4 data message byte 0 5 data message byte 1 6?7 reserved 8 reserved 9?ffh reserved table 5-53. command types (sheet 1 of 2) command type description 0 reserved 1 wake/smi#. this command wakes the system if it is not already awake. if system is already awake, an smi# is generated. note: the smb_wak_sts bit will be set by th is command, even if the system is already awake. the smi handler should then clear this bit. 2 unconditional powerdown. this command sets the pwrbtnor_sts bit, and has the same effect as the po werbutton override occurring. 3 hard reset without cycling: this command causes a hard reset of the system (does not include cycling of the powe r supply). this is equivalent to a write to the cf9h register with bits 2:1 set to 1, but bit 3 set to 0. 4 hard reset system. this command causes a ha rd reset of the system (including cycling of the power supply). this is equivalent to a write to the cf9h register with bits 3:1 set to 1. 5 disable the tco messages. this command will disa ble the intel ich10 from sending heartbeat and event messages (as described in section 5.14 ). once this command has been executed, heartbeat an d event message reporting can only be re-enabled by assertion and deas sertion of the rsmrst# signal. 6 wd reload: reload watchdog timer. 7 reserved http://www..net/ datasheet pdf - http://www..net/ functional description 224 datasheet 5.20.7.2 format of read command the external master performs byte re ad commands to the ich10 smbus slave interface. the ?command? field (bits 18:11) indicate which register is being accessed. the data field (bits 30:37) contain the value that should be read from that register. 8 smlink_slv_smi. when ich10 detects this command type while in the s0 state, it sets the smli nk_slv_smi_sts bit (see section 13.9.5 ). this command should only be used if the system is in an s0 state. if the message is received during s1?s5 states, the ich10 acknow ledges it, but the smlink_slv_smi_sts bit does not get set. note: it is possible that the system transitions out of the s0 state at the same time that the smlink_slv_smi command is received. in this case, the smlink_slv_smi_sts bit may get set bu t not serviced before the system goes to sleep. once the system returns to s0, the smi associated with this bit would then be generated. software mu st be able to handle this scenario. 9-ffh reserved. table 5-53. command types (sheet 2 of 2) command type description table 5-54. slave read cycle format bit description driven by comment 1 start external microcontroller 2-8 slave address - 7 bits external microcontroller must match value in receive slave address register 9 write external microcontroller always 0 10 ack intel ich10 11-18 command code ? 8 bits external microcontroller indicates which register is being accessed. see ta b l e 5 - 5 5 below for list of impl emented registers. 19 ack intel ich10 20 repeated start external microcontroller 21-27 slave address - 7 bits external microcontroller must match value in receive slave address register 28 read external microcontroller always 1 29 ack intel ich10 30-37 data byte intel ich10 value depends on register being accessed. ta b l e 5 - 5 5 below for list of implemented registers. 38 not ack external microcontroller 39 stop external microcontroller http://www..net/ datasheet pdf - http://www..net/ datasheet 225 functional description table 5-55. data values for slave read registers (sheet 1 of 2) register bits description 07:0 reserved for capabilities indication. should always return 00h. future chips may return another value to indicate different capabilities. 12:0 system power state 000 = s0 001 = s1 010 = reserved 011 = s3 100 = s4 101 = s5 110 = reserved 111 = reserved 7:3 reserved 23:0 reserved 7:4 reserved 35:0 watchdog timer current value note that watchdog timer has 10 bits, but this field is only 6 bits. if the current value is greater than 3fh, ich10 will always report 3fh in this field. 7:6 reserved 40 1 = the intruder detect (intrd_det) bit is set. this indicates that the system cover has probably been opened. 1 (consumer only) 1 = bti temperature event occurred. this bit will be set if the intel ich10?s thrm# input signal is at a valid low voltage state. this bit will be clear if the thrm# input signal is at a valid high voltage state. note: this bit interprets the behavior if the thrm# pin as active low. this bit is set independent of the trm#_pol bit setting. 1 (corporate only) 1 = bti temperature event occurred. this bit will be se t if the intel ich10?s thrm# input signal is acti ve. else this bit will read 0. note: the thrm# pin is in core well and accurate reflection of the thrm# pin is dependent on the platform being in s0. 2 doa cpu status . this bit will be 1 to indicate that the processor is dead 3 1 = second_to_sts bit set. this bit will be set after the second time-out (second_to_sts bit) of the watchdog timer occurs. 6:4 reserved. will always be 0, but software should ignore. 7 reflects the value of the gpio[11]/smbalert# pin (and is dependent upon the value of the gpi_inv[11] bit. if the gpi_inv[11] bit is 1, then the value in this bit equals the level of the gpi[11]/smbalert# pin (high = 1, low = 0). if the gpi_inv[11] bit is 0, then the value of this bit will equal the inverse of the level of the gpio[11]/smbalert# pin (high = 0, low = 1). 5 0 fwh bad bit. this bit will be 1 to indicate that the fwh read returned ffh, which indicates that it is probably blank. 1 reserved 2 cpu power failure status: ?1? if the cpupwr_flr bit in the gen_pmcon_2 register is set. 3 init# due to receiving shutdown message: this event is visible from the reception of the shutdown message until a platform reset is done if the shutdown policy select bit (sps) is configured to drive init#. when the sps bit is configur ed to generate pltrst# based on shutdown, this register bi t will always return 0. events on signal will not create a event message 4 reserved http://www..net/ datasheet pdf - http://www..net/ functional description 226 datasheet 5.20.7.2.1 behavioral notes according to smbus protocol, read and write messages always begin with a start bit ? address? write bit sequence. when the ich10 detects that the address matches the value in the receive slave address register, it will assume that the protocol is always followed and ignore the write bit (bit 9) and signal an acknowledge during bit 10. in other words, if a start ?address?read occurs (which is invalid for smbus read or write protocol), and the address matches the ich1 0?s slave address, the ich10 will still grab the cycle. also according to smbus protocol, a read cycle contains a repeated start?address? read sequence beginning at bit 20. once again, if the address matches the ich10?s receive slave address, it will assume that th e protocol is followed, ignore bit 28, and proceed with the slave read cycle. note: an external microcontroller must not atte mpt to access the ich10?s smbus slave logic until at least 1 second after both rtcr st# and rsmrst# are deasserted (high). 5.20.7.3 slave read of rtc time bytes the ich10 smbus slave interface allows exte rnal smbus master to read the internal rtc?s time byte registers. the rtc time bytes are internally latched by the ich10?s hardware whenever rtc time is not changing and smbus is idle. this en sures that the time byte delivered to the slave read is always valid and it does not change when the read is still in progress on the bus. the rtc time will change whenever ha rdware update is in progress, or there is a software write to the rtc time bytes. 5 power_ok_bad: indicates the failure core power well ramp during boot/resume. this bit will be active if the slp_s3# pin is de-asserted and pwrok pin is not asserted. 6 thermal trip: this bit will shadow the state of processor thermal trip status bit (cts) (16.2.1.2, gen_pmcon_2, bit 3). events on signal will not create a event message 7 reserved: default value is ?x? note: software should no t expect a consistent value when this bit is read through smbus/smlink 67:0 contents of the messag e 1 register. refer to section 13.9.8 for the description of this register. 77:0 contents of the messag e 2 register. refer to section 13.9.8 for the description of this register. 87:0 contents of the tco_wd cnt register. refer to section 13.9.9 for the description of this register. 9 7:0 seconds of the rtc a 7:0 minutes of the rtc b7:0hours of the rtc c 7:0 ?day of week? of the rtc d 7:0 ?day of month? of the rtc e 7:0 month of the rtc f7:0year of the rtc 10h?ffh 7:0 reserved table 5-55. data values for slave read registers (sheet 2 of 2) register bits description http://www..net/ datasheet pdf - http://www..net/ datasheet 227 functional description the ich10 smbus slave interface only suppor ts byte read operation. the external smbus master will read the rtc time bytes one after another. it is software?s responsibility to check and manage the possible time rollover when subsequent time bytes are read. for example, assuming the rtc time is 11 hours: 59 minutes: 59 seconds. when the external smbus master reads the hour as 11, then proceeds to read the minute, it is possible that the rollover happens between the reads and the minute is read as 0. this results in 11 hours: 0 minute instead of the correct time of 12 hours: 0 minutes. unless it is certain that rollover will not occur, software is required to detect the possible time rollover by reading multiple times such th at the read time by tes can be adjusted accordingly if needed. 5.20.7.4 format of host notify command the ich10 tracks and responds to the standa rd host notify command as specified in the system management bus (smbus) specification, version 2.0. the host address for this command is fixed to 0001000b. if the ich10 already has data for a previously- received host notify command which has not been serviced yet by the host software (as indicated by the host_notify_sts bit), then it will nack following the host address byte of the protocol. this allows the host to communicate non-acceptance to the master and retain the host notify address and data values for the previous cycle until host software completely services the interrupt. note: host software must always clear the host_notify_sts bit after completing any necessary reads of the address and data registers. ta b l e 5 - 5 6 shows the host notify format. table 5-56. host notify format bit description driven by comment 1 start external master 8:2 smb host address ? 7 bits external master always 0001_000 9 write external master always 0 10 ack (or nack) intel ? ich10 ich10 nacks if host_notify_sts is 1 17:11 device address ? 7 bits external master indicates the address of the master; loaded into the notify device address register 18 unused ? always 0 external master 7-bit-only address; th is bit is inserted to complete the byte 19 ack ich10 27:20 data byte low ? 8 bits external master loaded into the notify data low byte register 28 ack ich10 36:29 data byte high ? 8 bits external master loaded into the notify data high byte register 37 ack ich10 38 stop external master http://www..net/ datasheet pdf - http://www..net/ functional description 228 datasheet 5.21 intel ? high definition audio overview the ich10?s high definition audio (hda) controller communicates with the external codec(s) over the intel high definition audio serial link. the controller consists of a set of dma engines that are used to move samples of digitally encoded data between system memory and an external codec(s) . the ich10 implements four output dma engines and 4 input dma engines. the output dma engines move digital data from system memory to a d-a converter in a code c. ich10 implements a single serial data output signal (hda_sdout) that is connected to all external codecs. the input dma engines move digital data from the a-d converter in the codec to system memory. the ich10 implements four serial digital inpu t signals (hda_sdi[3:0]) supporting up to four codecs. audio software renders outbound and processes inbound data to/from buffers in system memory. the location of individual buffers is described by a buffer descriptor list (bdl) that is fetched and processed by the controller. the data in the buffers is arranged in a predefined format. the output dma engines fetch the digital data from memory and reformat it based on the programmed sample rate, bit/sample and number of channels. the data from the ou tput dma engines is then combined and serially sent to the external codecs over th e intel high definition audio link. the input dma engines receive data from the codecs over the intel high definition audio link and format the data based on the programmable attributes for that stream. the data is then written to memory in the predefined format for software to process. each dma engine moves one stream of data. a single codec can accept or generate multiple streams of data, one for each a-d or d-a converter in the codec. multiple codecs can accept the same output stream processed by a single dma engine. codec commands and responses are also transported to and from the codecs using dma engines. 5.22 intel ? active management technology (intel ? amt) (corporate only) intel active management technology is a set of advanced manageability features developed as a direct result of it custom er feedback gained through intel market research. reducing the total cost of ownership (tco) through improved asset tracking, remote manageability, and fewer desk-side visi ts were identified as key it priorities. intel amt extends the capabilities of existi ng management solutions by making the asset information, remote diagnostics, recovery and contain capabilities always available, or out of band (oob), even when the system is in a low-power ?off? state or the os is hung. another feature of intel amt is system defense. system defense is used to stop the propagation of worms and viruses. programmab le packet filters in the integrated lan controller are used to accomplish this. th ese filters inspect all incoming and all outgoing packets and decide whether to block or pass the packets as configured. there is no indication to the host that a packet has been blocked or accepted. the logic can be used to accept or block reception to host or transmission to network paths. additionally, counter logic can be used to count the number or filter matches for a given filter. this feature allows for statistical sampling of connections as well as rate limiting of connections. http://www..net/ datasheet pdf - http://www..net/ datasheet 229 functional description 5.22.1 intel ? amt features ? e-asset tag ? oob hw and sw inventory logs ?oob alerts ?ide redirect ? serial over lan for remote control ? remote diagnostics execution ? os lock-up alert ?os repair ? remote bios recovery and update 5.22.2 intel ? amt requirements intel amt is a platform-level solution th at utilizes multiple system components including: ?intel amt-ready ich10 sku ? intel gigabit ethernet phy (intel ? 82567 gigabit platform lan connect device) with intel active management technology for remote access ? spi flash memory with 4kb or 8kb sector erase that meets requirements set in section 5.23.4 (32 mb minimum for intel amt) to store asset information, management software code, and logs ? bios to provide asset detection and post diagnostics (bios and intel amt can optionally share same flash memory device) ? familiar isv software packages to take advantage of intel amt?s platform management capabilities 5.23 serial peripheral interface (spi) the serial peripheral interface (spi) is a 4-pin interface that provides a lower-cost alternative for system flash versus the firmware hub on the lpc bus. the 4-pin spi interface consists of clock (c lk), master data out (master out slave in (mosi)), master data in (master in slave out (miso)) and an active low chip select (spi_cs[1:0]#). the ich10 supports up to tw o spi flash devices using two separate chip select pins. each spi flash device can be up to 16 mb ytes. the ich10 spi interface supports 20 mhz and 33 mhz spi devices. communication on the spi bus is done with a master ? slave protocol. the slave is connected to the ich10 and is implemented as a tri-state bus. note: if option 11 lpc is selected bios may still be placed on lpc, but all platforms with ich10 (corporate only) require spi flash conne cted directly to the ich's spi bus with a valid descriptor in order to boot. note: when spi is selected by the boot bios dest ination strap and a spi device is detected by the ich10, lpc based bios flash is disabled. http://www..net/ datasheet pdf - http://www..net/ functional description 230 datasheet 5.23.1 spi supported feature overview spi flash on the ich10 has two operationa l modes, descriptor and non-descriptor. 5.23.1.1 non-descriptor mode non-descriptor mode is similar to the flash functionality of ich7. in this mode, spi flash can only be used for bios. direct re ad and writes are not supported. bios has read/write access only through register accesses. through those register accesses bios can read and write to the entire flash without security checking. there is also no support for the integrated gigabit ethernet , intel management engine, chipset soft straps, as well multiple spi flash components. 5.23.1.2 descriptor mode descriptor mode enables many new features of the chipset: ? integrated gigabit ethernet and host processor for gigabit ethernet software ? intel active management technology ? intel quiet system technology ? supports two spi flash components using two separate chip select pins ? hardware enforced security restricting master accesses to different regions ? chipset soft strap region provides the ability to use flash nvm as an alternative to hardware pull-up/pull-down resistors for both ich and (g)mch ? supports the spi fast read instruction and frequencies of 33 mhz ? uses standardized flash instruction set 5.23.1.2.1 spi flash regions in descriptor mode the flash is divided into five separate regions: only three masters can access the four regions: host processor running bios code, integrated gigabit ethernet and host processor running gigabit ethernet software, and intel management engine. the only required region is region 0, the flash descriptor. region 0 must be located in the first sector of device 0 (offset 0). flash region sizes spi flash space requirements differ by platfo rm and configuration. the flash descriptor requires one 4 kb or larger block. gbe requires two 4 kb or larger blocks. the platform data region is 32 kb. the amount of flash space consumed is dependent on the erase granularity of the flash part and the platform requirements for the intel me and bios regions. the intel me region will contain firmware to support intel quiet system technology, intel active management technology, asf 2.0 and intel trusted platform module. region content 0 flash descriptor 1bios 2 intel management engine 3 gigabit ethernet 4platform data http://www..net/ datasheet pdf - http://www..net/ datasheet 231 functional description 5.23.1.3 device partitioning the ich10 spi flash controller supports two sets of attributes in spi flash space. this allows for supporting an asymmetric flash component that has two separate sets of attributes in the upper and lower part of th e memory array. an example of this is a flash part that has different erase granularities in two different parts of the memory array. this allows for the usage of two separate flash vendors if using two different flash parts. table 5-57. region size versus er ase granularity of flash components region size with 4 kb blocks size with 64 kb blocks descriptor 4 kb 64 kb gbe 8 kb 128 kb platform data region 32 kb not supported bios varies by platform varies by platform intel me varies by platform varies by platform figure 5-16. flash partition boundary lower fl ash partition upper flash partition ? ? fl ash parti ti on boundary http://www..net/ datasheet pdf - http://www..net/ functional description 232 datasheet 5.23.2 flash descriptor the maximum size of the flash descriptor is 4 kb. if the block/sector size of the spi flash device is greater than 4 kb, the flash descriptor will only use the first 4 kb of the first block. the flash descriptor requires its own block at the bottom of memory (0x00h). the information stored in the flas h descriptor can only be written during the manufacturing process as its read/write permi ssions must be set to read only when the computer leaves the manufacturing floor. the flash descriptor is made up of eleven sections: 1. the flash signature selects descriptor mode as well as verifies if the flash is programmed and functioning. the data at th e bottom of the flash (offset 0) must be 0ff0a55ah in order to be in descriptor mode. 2. the descriptor map has pointers to the other five descriptor sections as well as the size of each. figure 5-17. flash descriptor sections descriptor map component signature region master ich soft straps reserved 0 4kb management engine vscc table descriptor upper map oem section mch soft straps http://www..net/ datasheet pdf - http://www..net/ datasheet 233 functional description 3. the component section has information abou t the spi flash in the system including: the number of components, density of ea ch, invalid instructions (such as chip erase), and frequencies for read, fast read and write/erase instructions. 4. the region section points to the three other regions as well as the size of each region. 5. the master region contains the security settings for the flash, granting read/write permissions for each region and identifying each master by a requestor id. see section 5.23.2.1 for more information. 6 & 7. the (g)mch and ich chipset soft strap sections contain (g)mch and ich configurable parameters. 8. the reserved region between the top of the (g)mch strap section and the bottom of the oem section is reserved for future chipset usages. 9. the descriptor upper map determines th e length and base address of the intel management engine vscc table. 10. the intel management engine vscc table holds the jedec id and the vscc information of the entire spi flash supported by the nvm image. 11. oem section is 256 bytes reserved at the top of the flash descriptor for use by oem. 5.23.2.1 descriptor master region the master region defines read and write access setting for each region of the spi device. the master region recognizes three masters: bios, gigabit ethernet, and intel management engine. each master is only a llowed to do direct reads of its primary regions. table 5-58. region access control table master read/write access region cpu and bios intel me/(g)mch gbe controller descriptor n/a n/a n/a bios cpu and bios can always read from and write to bios region read / write read / write intel management engine read / write intel me can always read from and write to intel me region read / write gigabit ethernet read / write read / write gbe software can always read from and write to gbe region platform data region n/a n/a n/a http://www..net/ datasheet pdf - http://www..net/ functional description 234 datasheet 5.23.3 flash access there are two types of flash accesses: direct access: ? masters are allowed to do direct read only of their primary region ? gigabit ethernet region can only be directly accessed by the gigabit ethernet controller. gigabit ethernet software must use program registers to access the gigabit ethernet region. ? master's host or intel management engine virtual read address is converted into the spi flash linear address (fla) using the flash descriptor region base/limit registers program register access: ? program register accesses are not allowed to cross a 4 kb boundary and can not issue a command that might extend across two components ? software programs the fla corresp onding to the region desired ? software must read the devices primary region base/limit address to create a fla. 5.23.3.1 direct access security ? requester id of the device must match that of the primary requester id in the master section ? calculated flash linear address must fall between primary region base/limit ? direct write not allowed ? direct read cache contents are reset to 0s on a read from a different master ? supports the same cache flush mechanism in the ich7, which includes program register writes 5.23.3.2 register access security ? only primary region masters can access the registers note: processor running gigabit ethernet softwa re can access gigabit ethernet registers ? masters are only allowed to read or wr ite those regions they have read/write permission ? using the flash region access permissions, one master can give another master read/write permissions to their area ? using the five protected range registers, each master can add separate read/write protection above that granted in the flash descriptor for their own accesses ? example: bios may want to protect different regions of bios from being erased ? ranges can extend across region boundaries http://www..net/ datasheet pdf - http://www..net/ datasheet 235 functional description 5.23.4 serial flash device compatibility requirements a variety of serial flash devices exist in th e market. for a serial flash device to be compatible with the intel ich10 spi bus, it must meet the minimum requirements detailed in the following sections. 5.23.4.1 intel ? ich10 spi based bios requirements a serial flash device must meet the fo llowing minimum requirements when used explicitly for system bios storage. ? erase size capability of at least one of the following: 64 kb, 8 kb, 4 kb, or 256 bytes. ? device must support multiple writes to a page without requiring a preceding erase cycle (refer to section 5.23.5 ) ? serial flash device must ignore the upper address bits such that an address of ffffffh aliases to the top of the flash memory. ? spi compatible mode 0 support (clock phase is 0 and data is latched on the rising edge of the clock). ? if the device receives a command that is not supported or incomplete (less than 8 bits), the device must complete the cycle gracefully without any impact on the flash content. ? an erase command (page, sector, block, chip, etc.) must set all bits inside the designated area (page, sector, block, chip, etc.) to 1 (fh). ? status register bit 0 must be set to 1 when a write, erase or write to status register is in progress and cleared to 0 when a write or erase is not in progress. ? devices requiring the write enable co mmand mst automatically clear the write enable latch at the end of data program instructions. ? byte write must be supported. the flexib ility to perform a write between 1 byte to 64 bytes is recommended. ? hardware sequencing requirements are optional in bios only platforms. ? spi flash parts that do not meet hardware sequencing command set requirements may work in bios only platforms via software sequencing. 5.23.4.2 integrated lan firm ware spi flash requirements a serial flash device that will be used for system bios and integrated lan or integrated lan only must meet all the spi based bios requirements plus: ? hardware sequencing ? 4, 8 or 64 kbytes erase capability must be supported. 5.23.4.2.1 spi flash unlocking re quirements for integrated lan bios must ensure there is no spi flash ba sed read/write/erase protection on the gbe region. gbe firmware and drivers for the integr ated lan need to be able to read, write and erase the gbe region at all times. 5.23.4.3 intel ? management engine firmware spi flash requirements intel management engine firmware must me et the spi flash based bios requirements plus: ? hardware sequencing. ? flash part must be uniform 4 kb erasab le block throughout the entire device. ? write protection scheme must meet spi flash unlocking requirements for intel management engine. http://www..net/ datasheet pdf - http://www..net/ functional description 236 datasheet 5.23.4.3.1 spi flash unlo cking requirements for intel management engine flash devices must be globally unlocked (read, write and erase access on the intel me region) from power on by writing 00h to the flash?s status register to disable write protection. if the status register must be unprotected, it must use the enable write status register command 50h or write enable 06h. opcode 01h (write to status register) must then be used to write a single byte of 00h into the status register. this must unlock the entire part. if the spi flash?s status register has non-volatile bits that must be written to, bits [5:2] of the flash?s status register must be all 0h to indicate that the flash is unlocked. if there is no need to execute a write enab le on the status register, then opcodes 06h and 50h must be ignored. after global unlock, bios has the ability to lock down small sections of the flash as long as they do not involve the intel me or gbe region. 5.23.4.4 hardware sequ encing requirements ta b l e 5 - 5 9 contains a list of commands and the associated opcodes that a spi-based serial flash device must support in order to be compatible with hardware sequencing. 5.23.4.4.1 jedec id since each serial flash device may have unique capabilities and commands, the jedec id is the necessary mechanism for identify ing the device so the uniqueness of the device can be comprehended by the controlle r (master). the jedec id uses the opcode 9fh and a specified implementation an d usage model. this jedec standard manufacturer and device id read method is defined in standard jesd21-c, prn03-nv. table 5-59. hardware sequencing commands and opcode requirements commands opcode notes write to status register 01h writes a byte to spi flash?s status register. enable write to status register command must be run prior to this command. program data 02h single byte or 64 byte write as determined by flash part capabilities and software. read data 03h write disable 04h read status 05h outputs contents of spi flash?s status register write enable 06h fast read 0bh enable write to status register 50h or 60h enables a bit in the status regi ster to allow an update to the status register erase program mable 256b, 4 kbyte, 8 kbyte or 64 kbyte full chip erase c7h jedec id 9fh see section . http://www..net/ datasheet pdf - http://www..net/ datasheet 237 functional description 5.23.5 multiple page write usage model the system bios and intel active management technology firmware usage models require that the serial flash device support multiple writes to a page (minimum of 512 writes) without requiring a preceding erase command. bios commonly uses capabilities such as counters that are used for error logging and system boot progress logging. these counters are typically implem ented by using byte-writes to ?increment? the bits within a page that have been designated as the counter. the intel amt firmware usage model requires the capabilit y for multiple data updates within any given page. these data updates occur via byte-writes without executing a preceding erase to the given page. both the bios and intel amt firmware multiple page write usage models apply to sequential and non-sequential data writes. note: this usage model requirement is based on an y given bit only being written once from a 1-to-0 without requiring the preceding erase. an erase would be required to change bits back to the 1 state. 5.23.5.1 soft flash protection there are two types of flash protection that are not defined in the flash descriptor supported by ich10: 1. bios range write protection 2. smi#-based global write protection both mechanisms are logically or?d togeth er such that if any of the mechanisms indicate that the access should be blocked, then it is blocked. ta b l e 5 - 6 0 provides a summary of the mechanisms. a blocked command will appear to software to finish, except that the blocked access status bit is set in this case. 5.23.5.2 bios range write protection the ich10 provides a method for blocking wr ites to specific ranges in the spi flash when the protected bios ranges are enabled. this is achieved by checking the opcode type information (which can be locked down by the initial boot bios) and the address of the requested command agai nst the base and limit fields of a write protected bios range. note: once bios has locked down the protected bios range registers, this mechanism remains in place until the next system reset. table 5-60. flash protec tion mechanism summary mechanism accesses blocked range specific? reset-override or smi#- override? equivalent function on fwh bios range write protection writes yes reset override fwh sector protection write protect writes no smi# override same as write protect in previous ichs for fwh http://www..net/ datasheet pdf - http://www..net/ functional description 238 datasheet 5.23.5.3 smi# based global write protection the ich provides a method for blocking writes to the spi flash when the write protected bit is cleared (i.e., protected). this is achieved by checking the opcode type information (which can be locked down by the initial boot bios) of the requested command. the write protect and lock enable bits inte ract in the same manner for spi bios as they do for the fwh bios. 5.23.6 flash device configurations the ich10-based platform may use the serial flash in multiple configurations. the following table focuses on the supported co nfigurations involving the ich10 and intel active management technology. note: when spi is selected for bios and a spi de vice is detected by the ich10, lpc based bios flash is disabled. note: firmware includes intel active management technology, asf, intel quiet system technology and gigabit ethernet. 5.23.7 spi flash device recommended pinout the table below contains the recommended serial flash device pin-out for an 8-pin device. use of the recommended pin-out on an 8-pin device reduces complexities involved with designing the serial flash device onto a motherboard and allows for support of a common footprint usage model (refer to section 5.23.8.1 ). although an 8-pin device is preferred over a 16-pin device due to footprint compatibility, the following table contains th e recommended serial flash device pin-out for a 16-pin soic. configuration system bios storage intel ? ich10 firmware minimum number of spi device(s) 1spino 1 2non-spiyes 1 3spiyes 1 4non-spino 0 table 5-61. recommended pinout for 8-pin serial flash device pin # signal 1chips select 2 data output 3 write protect 4ground 5 data input 6serial clock 7hold / reset 8 supply voltage http://www..net/ datasheet pdf - http://www..net/ datasheet 239 functional description 5.23.8 serial flash device package 5.23.8.1 common footprint usage model to minimize platform motherboard redesign and to enable platform bill of material (bom) selectability, many pc system oem?s design their motherboard with a single common footprint. this common footprint allows population of a soldered down device or a socket that accepts a leadless device . this enables the board manufacturer to support, via selection of the appropriate bom, either of these solutions on the same system without requiring any board redesign. the common footprint usage model is desirable during system debug and by flash content developers since the leadless device can be easily removed and reprogrammed without damage to device leads. when the board and flash content is mature for high- volume production, both the socketed leadle ss solution and the soldered down leaded solution are available through bom selection. 5.23.8.2 serial flash devi ce package recommendations it is highly recommended that the common footprint usage model be supported. an example of how this can be accomplished is as follows: ? the recommended pinout for 8-pin seri al flash devices is used (refer to section 5.23.7 ). ? the 8-pin device is supported in either an 8-contact vdfpn (6x5 mm mlp) package or an 8-contact wson (5x6 mm) package. these packages can fit into a socket that is land pattern compatible with the wide body so8 package. ? the 8-pin device is supported in the so8 (150 mil) and in the wide-body so8 (200 mil) packages. the 16-pin device is supported in the so16 (300 mil) package. table 5-62. recommended pinout for 16-pin serial flash device pin # signal pin # signal 1 hold / reset 9 write protect 2 supply voltage 10 ground 3 no connect 11 no connect 4 no connect 12 no connect 5 no connect 13 no connect 6 no connect 14 no connect 7 chip select 15 serial data in 8 serial data out 16 serial clock http://www..net/ datasheet pdf - http://www..net/ functional description 240 datasheet 5.24 intel ? quiet system technology (intel ? qst) the ich10 implements three pwm and 4 tach signals for intel quiet system technology (qst). note: intel quiet system technology functionalit y requires a correctly configured system, including an appropriate (g)mch with inte l me, intel me firmware, and system bios support. 5.24.1 pwm outputs this signal is driven as open-drain. an exte rnal pull-up resistor is integrated into the fan to provide the rising edge of the pwm ou tput signal. the pwm output is driven low during reset, which represents 0% duty cycl e to the fans. after reset de-assertion, the pwm output will continue to be driven low until one of the following occurs: ? the internal pwm control register is programmed to a non-zero value by the intel qst firmware. ? the watchdog timer expires (enabled and set at 4 seconds by default). ? the polarity of the signal is in verted by the intel qst firmware. note that if a pwm output will be programmed to inverted polarity for a particular fan, then the low voltage driven during reset represents 100% duty cycle to the fan. 5.24.2 tach inputs this signal is driven as an open-collector or open-drain output from the fan. an external pull-up is expected to be impl emented on the motherboard to provide the rising edge of the tach input. this signal has analog hysteresis and digital filtering due to the potentially slow rise and fall times. this signal has a weak internal pull-up resistor to keep the input buffer from floati ng if the tach input is not connected to a fan. 5.25 thermal sensors ich10 integrates two thermal sensors that mo nitor the temperature within its die. the thermal sensors are used for intel quiet system technology (intel qst). the intel qst firmware can internally access the temperature measured by the sensors and use the data as a factor to determine how to control the fans. the ich10 thermal sensors also provide th e capability to protect the ich10 under a catastrophic thermal situation. when the sensors are enabled and correctly programmed by the system bios, the ich10 will shut down the system when the ich10 thermal limit is reached. refer to the thermal memory mapped configuration registers section 23.2 for more info on the catastrophic settings. http://www..net/ datasheet pdf - http://www..net/ datasheet 241 functional description 5.26 feature capability mechanism a set of registers is included in the ich10 lpc interface (device 31, function 0, offset e0h - ebh) that allows the system software or bios to easily determine the features supported by ich10. these registers can be accessed through lpc pci configuration space, thus allowing for convenient single point access mechanism for chipset feature detection. this set of registers consists of: capability id (fdcap) capability length (fdlen) capability version and vendor-s pecific capability id (fdver) feature vector (fvect) 5.27 integrated trusted platform module (corporate only) the integrated trusted platform module (t pm) implementation consists of firmware, intel management engine resources and dedicated hardware within the ich and the (g)mch. the integrated tpm supports all requ irements of the tpm specification version 1.2, level 2 revision 103, as published by the trusted computing group. note: integrated tpm functionality requires a co rrectly configured system, including an appropriate (g)mch with intel management engine firmware, ich10 and spi flash. 5.27.1 integrated tpm hardware requirements the following hardware components are required for tpm 1.2 functionality: 1. spi flash memory: the spi flash componen t connected to the ich (spi interface) provides non-volatile storage requirement for the integrated tpm. it contains the fw code which is loaded by the inte l management engine upon power on. 2. monotonic counters: the ich10 contains four tpm 1.2 compliant monotonic counters that reside in the rtc well whic h maintains values programmed by the integrated tpm across power cycles. the counters are only incremented by tpm software (host or intel me) and are not controlled by the ich hardware. 3. physical presence: physical presence indication is required in order to enable certain tpm commands. these commands are generally used to bypass owner authorized commands when the authorization data is unavailable or to set the integrated tpm to a non-owner state. the intel management engine firmware uses the tpm_pp pin on the ich10 to indicate ph ysical presence to the platform when pulled high. in addition, physical presence flags can be set to force physical presence by firmware. 4. chipset: an ich10 and (g)mch with inte l management engine enabled is required for integrated tpm support. http://www..net/ datasheet pdf - http://www..net/ functional description 242 datasheet 5.27.2 enabling integrated tpm the integrated tpm is enabled based on the combination of a functional straps on both the ich and the (g)mch and a soft strap bi t found in the spi descriptor. when the integrated tpm is enabled, front side bus cy cles that would otherwise propagate to the lpc bus will be routed by the config bus de coder to the integrated tpm host decoder. either functional strap or the soft strap bi t may be used to disable the integrated tpm. ? ich functional strap : the ich10 enables integrated tpm when spi_mosi is sampled high on the rising edge of clpwrok and disabled if the spi_mosi signal is sampled low. see section 2.25.1 for details. the spi_mosi signal requires an external pull-up resistor to enable the in tegrated tpm. spi_mosi has an integrated pull-down resistor enabled at reset only an d does not require an external pull-down resistor to disable integrated tpm. ? soft strap : the integrated tpm disable bit (bit 2) in the (g)mchstrp0 register (fsmba + 0h) within the flash descriptor can act as an override to the functional straps on both the ich and (g)mch. when set, the integrated tpm will be disabled regardless of the values of the functional straps on the ich and/or (g)mch. this bit along with both functional straps must be appropriately configured to enable integrated tpm. ? (g)mch functional strap: for (g)mch functional strap information, consult the appropriate (g)mch documentation. http://www..net/ datasheet pdf - http://www..net/ datasheet 243 ballout definition 6 ballout definition this chapter contains the intel ? ich10 ballout information. 6.1 intel ? ich10 ballout this section contains the ich10 ballout. figure 6-1 and figure 6-2 show the ballout from a top of the package view. ta b l e 6 - 1 is the bga ball list, sorted alphabetically by signal name. note: notes for figure 6-1 , figure 6-2 , and ta b l e 6 - 1 1. symbol indicates a particular use of a pin is cunsumer only. 2. ? symbol indicates a particular use of a pin is corporate only. http://www..net/ datasheet pdf - http://www..net/ ballout definition 244 datasheet figure 6-1. intel ? ich10 ballout (top view?left side) 123456789101112131415 a vss vcc3_3 pirqd# ad11 ad4 v5ref gnt1# / gpio51 gpio12 gpio14 / jtagdi ? / qst_bmbu sy# vcclan1_1 gpio27 vcclan3_3 slp_s3# gpio24 / mem_led smlink0 a b vcc3_3 vss pciclk ad9 vss ad8 ad7 vss vcc3_3 vcclan1_1 vss vcclan3_3 slp_s4# vss smlink1 b c ad24 ad25 ad26 c/be2# ad14 devsel# gnt2# / gpio53 ad1 ad3 ad0 s4_state# / gpio26 gpio57 / tpm_pp / jtagtck ? gpio72 ? / tp0 pltrst# stp_pci# / gpio15 c d ad27 ad15 ad21 d e pirqb# vss par ad16 trdy# ad10 c/be3# ad2 ad6 ad18 ad5 lan_rxd2 lan_rsts ync vss e f pirqc# pirqg# / gpio4 ad29 perr# vss gnt3# / gpio55 ad13 vss stop# c/be0# vss req2# / gpio52 lan_txd1 lan_txd0 f g ad30 pirqh# / gpio5 vcc3_3 ad23 ad20 ad17 req3# / gpio54 c/be1# ad19 vcc3_3 frame# req1# / gpio50 lan_txd2 lan_rxd0 g h fwh1 / lad1 vss ad31 gnt0# ad22 vcc3_3 plock# vss vcc1_5_a vcc1_5_a ad12 vss lan_rxd1 vccsus3_3 h j fwh3 / lad3 vcc3_3 ldrq1# / gpio23 pirqa# vss ad28 irdy# j k gpio18 gpio32 fwh0 / lad0 serr# pirqe# / gpio2 req0# vcc3_3 k l sataclkr eq# / gpio35 vss rcin# fwh4 / lframe# ldrq0# pirqf# / gpio3 vcc3_3 l m oc7# / gpio31 gpio16 / dprslpvr init3_3v# clk14 vss fwh2 / lad2 vss vcc1_1 vcc1_1 vss vcc1_1 m n oc5# / gpio29 oc4# / gpio43 oc1# / gpio40 oc6# / gpio30 serirq gpio0 / bmbusy# spkr vcc1_1 vss vss vss n p oc11# / gpio47 vss oc8# / gpio44 oc0# / gpio59 vss oc2# / gpio41 a20gate vss vss vss vss p r sus_stat# / lpcpd / gpio61 ? pcirst# pme# susclk / gpio62 ? oc9# / gpio45 oc3# / gpio42 vss vcc1_1 vss vss vss r t vcc1_5_a vss pwrbtn# vss clpwrok oc10# / gpio46 ck_pwrg d vss vss vss vss t u vccsus3_3 vccsus3_3 vccsus3_3 vccsus3_3 vccsus3_3 vccsus3_3 vccsus3_3 vcc1_1 vss vss vss u v usbp11n usbp11p vss usbp9p usbp9n vss vccsus3_3 vcc1_1 vss vss vss v w vss usbp10n usbp10p vss vss vccsus3_3 vccsus3_3 vcc1_1 vcc1_1 vss vcc1_1 w y usbp8n usbp8p vss usbp6p usbp6n vss vccsus3_3 y aa vss usbp7p usbp7n vss vss vcc1_5_a vcc1_5_a aa ab usbp5n usbp5p vss usbp3p usbp3n vcc1_5_a vcc1_5_a ab ac vss usbp4p usbp4n vss vss vccsus1_1 vss vccsushda vcchda vcc1_5_a vss vcc1_5_a vcc1_5_a vcc1_5_a ac ad usbp2n usbp2p vss usbp0p usbp0n vss vccsus1_5 vss vcc3_3 vcc1_5_a vcc1_5_a vcc1_5_a vss vss ad ae vss usbp1p usbp1n vss vss sataled# vss vss vss vcc1_5_a vss vss vss vss ae af v5ref_sus vccsus3_3 vss gpio20 gpio33 vss sata5txn vss sata4txn vcc1_5_a sata3txn vss sata2txp vss af ag usbrbias# usbrbias clk48 ag ah hda_sdin2 vss hda_bit_c lk hda_sdin1 gpio34 vss sata5txp vss sata4txp vcc1_5_a vcc1_5_a sata3txp vss sata2txn vss ah aj hda_rst# hda_sdou t hda_sdin3 vss vss satarbias sata5rxn vss sata4rxn vcc1_5_a sata3rxn vss sata2rxn vss sata1rxn aj ak hda_sync vss hda_sdin0 vcc3_3 vccusbpll satarbias # sata5rxp vss sata4rxp vcc1_5_a sata3rxp vss sata2rxp vss sata1rxp ak 123456789101112131415 http://www..net/ datasheet pdf - http://www..net/ datasheet 245 ballout definition figure 6-2. intel ? ich10 ballout (top view?right side) 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 a tp6 vccsus3_3 gpio9 gpio13 drampwr ok ? / gpio8 rtcx1 vccrtc vcccl1_1 vcc1_1 rtcrst# vcccl1_5 vccglan 3_3 vccglanpl l glan_com po vss a b tp7 vss stp_cpu# / gpio25 ? vss vccsus3_3 rtcx2 vss vcccl3_3 vcc1_1 vss spi_miso vss vss glan_com pi vccglan1_ 5 b c smbalert# / gpio11 / jtagtdo ? gpio10 / cpu_missi ng / jtagtms ? tp5 sst vccsus3_3 lan_rst# vrmpwrg d vcccl3_3 vcc1_1 pwrok spi_mosi cl_vref 0 vccglan1_ 5 vccglan1_ 5 vccglan1_ 5 c d vss pern6 / glan_rxn perp6 / glan_rxp d e smbdata vccsus3_3 vss tp4 wake# lan100_sl p vss intvrmen vcc1_1 spi_cs0# petn6 / glan_txn petp6 / glan_txp vss vss e f gpio56 slp_m# linkalert# / gpio60 / jtagrst# ? sys_rese t# tp3 vss rsmrst# spi_cs1# vcc1_1 glan_clk vss vss perp5 pern5 f g vss slp_s5# / gpio63 ? gpio28 ri# cl_rst0# intruder# cl_clk0 spi_clk vcc1_1 vss petn5 petp5 vss vss g h smbclk vccsus1_1 vccsus1_5 vss srtcrst# cl_data0 vss vcc1_1 vcc1_1 vss vss vss perp4 pern4 h j vcc1_1 vcc1_5_b vcc1_5_b petn4 petp4 vss vss j k vcc1_5_b vcc1_5_b vcc1_5_b vss vss perp3 pern3 k l vss vcc1_5_b vcc1_5_b petn3 petp3 vss vss l m vss vcc1_1 vcc1_1 vcc1_1 vcc1_5_b vcc1_5_b vcc1_5_b vss vss perp2 pern2 m n vss vss vss vcc1_1 vss vcc1_5_b vcc1_5_b petn2 petp2 vss vss n p vss vss vss vss vcc1_5_b vcc1_5_b vcc1_5_b vss vss perp1 pern1 p r vss vss vss vcc1_1 vss vcc1_5_b vcc1_5_b petn1 petp1 vss vss r t vss vss vss vss vcc1_5_b vcc1_5_b vcc1_5_b vcc1_5_b vcc1_5_b vss vccdmipll t u vss vss vss vcc1_1 vss vcc1_5_b dmi_clkp dmi_clkn vcc1_5_b vcc1_5_b vcc1_5_b u v vss vss vss vcc1_1 vcc1_5_b vcc1_5_b vcc1_5_b vss vss dmi0txp dmi0txn v w vss vcc1_1 vcc1_1 vcc1_1 vss vcc1_5_b vcc1_5_b dmi0rxp dmi0rxn vss vss w y vcc1_5_b vcc1_5_b vcc1_5_b vss vss dmi1txp dmi1txn y aa vcc1_5_b vcc1_5_b vcc1_5_b dmi1rxn dmi1rxp vss vss aa ab vcc1_5_a vcc1_5_b vcc1_5_b vss vss dmi2txp dmi2txn ab ac vcc1_5_a vcc1_5_a vcc1_5_a vcc3_3 vcc1_5_a vcc3_3 ignne# peci vss vcc1_5_b dmi2rxn dmi2rxp vss vss ac ad vss vcc1_5_a vss vss sdataout 1 / gpio48 sata5gp vss cpupwrg d thrmtrip# vcc1_5_b vcc1_5_b vcc1_5_b dmi3txn dmi3txp ad ae vss vcc1_5_a vss vss sata1gp / gpio19 sata2gp / gpio36 sata3gp / gpio37 init# dpslp# vss dmi3rxp vcc1_5_b vcc1_5_b vcc1_5_b ae af sata1txp vcc1_5_a sata_clkn sata_clk p vss vcc3_3 sata4gp vss nmi vss dmi3rxn dmi_irco mp vss dmi_zcom p af ag vss vccdmi vccdmi ag ah sata1txn vcc1_5_a vcc1_5_a vss vss tach0 / gpio17 tach2 / gpio6 sdataout 0 / gpio39 vcc3_3 mch_sync# smi# intr v_cpu_io vss vcc3_3 ah aj vss sata0rxp vcc1_5_a sata0txp vss pwm0 pwm1 vss sclock / gpio22 gpio49 vss ferr# a20m# stpclk# v_cpu_io aj ak vss sata0rxn vcc1_5_a sata0txn vccsatapl l tach1 / gpio1 pwm2 tach3 / gpio7 sload / gpio38 sata0gp / gpio21 thrm# vss dprstp# vss vss ak 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 http://www..net/ datasheet pdf - http://www..net/ 246 datasheet ballout definition table 6-1. intel ? ich10 ballout by signal name ball name ball # a20gate p8 a20m# aj28 ad0 c10 ad1 c8 ad2 e9 ad3 c9 ad4 a5 ad5 e12 ad6 e10 ad7 b7 ad8 b6 ad9 b4 ad10 e7 ad11 a4 ad12 h12 ad13 f8 ad14 c5 ad15 d2 ad16 e5 ad17 g7 ad18 e11 ad19 g10 ad20 g6 ad21 d3 ad22 h6 ad23 g5 ad24 c1 ad25 c2 ad26 c3 ad27 d1 ad28 j7 ad29 f3 ad30 g1 ad31 h3 c/be0# f11 c/be1# g9 c/be2# c4 c/be3# e8 ck_pwrgd t8 cl_clk0 g22 cl_data0 h21 cl_rst0# g20 cl_vref0 c27 clk14 m5 clk48 ag3 clpwrok t6 cpupwrgd ad23 devsel# c6 dmi_clkn u26 dmi_clkp u25 dmi_ircomp af28 dmi_zcomp af30 dmi0rxn w28 dmi0rxp w26 dmi0txn v30 dmi0txp v29 dmi1rxn aa26 dmi1rxp aa28 dmi1txn y30 dmi1txp y29 dmi2rxn ac26 dmi2rxp ac28 dmi2txn ab30 dmi2txp ab29 dmi3rxn af26 dmi3rxp ae26 dmi3txn ad29 dmi3txp ad30 drampwrok ? / gpio8 a20 ferr# aj27 frame# g12 fwh0 / lad0 k3 fwh1 / lad1 h1 fwh2 / lad2 m7 fwh3 / lad3 j1 fwh4 / lframe# l5 glan_clk f25 table 6-1. intel ? ich10 ballout by signal name ball name ball # glan_compi b29 glan_compo a29 gnt0# h5 gnt1# / gpio51 a7 gnt2# / gpio53 c7 gnt3# / gpio55 f7 gpio0 n7 gpio10 / cpu_missing / jtagtms ? c17 gpio12 a8 gpio13 a19 gpio14 / jtagtdi ? / qst_bmbusy# a9 gpio16 / dprslpvr m2 gpio18 k1 gpio20 af5 gpio24 a14 gpio27 a11 gpio28 g18 gpio32 k2 gpio33 af6 gpio34 ah5 gpio49 aj25 gpio56 f16 gpio57 / tpm_pp / jtagtck ? c12 gpio72 ? / tp0 c13 gpio9 a18 hda_bit_clk ah3 hda_rst# aj1 hda_sdin0 ak3 hda_sdin1 ah4 hda_sdin2 ah1 hda_sdin3 aj3 hda_sdout aj2 hda_sync ak1 ignne# ac22 init# ae23 init3_3v# m3 table 6-1. intel ? ich10 ballout by signal name ball name ball # http://www..net/ datasheet pdf - http://www..net/ datasheet 247 ballout definition intr ah27 intruder# g21 intvrmen e23 irdy# j8 lan_rst# c21 lan_rstsync e14 lan_rxd0 g15 lan_rxd1 h14 lan_rxd2 e13 lan_txd0 f15 lan_txd1 f14 lan_txd2 g14 lan100_slp e21 ldrq0# l6 ldrq1# / gpio23 j3 linkalert# / gpio60 / jtagrst# ? f18 mch_sync# ah25 nmi af24 oc0# / gpio59 p5 oc1# / gpio40 n3 oc2# / gpio41 p7 oc3# / gpio42 r7 oc4# / gpio43 n2 oc5# / gpio29 n1 oc6# / gpio30 n5 oc7# / gpio31 m1 oc8# / gpio44 p3 oc9# / gpio45 r6 oc10# / gpio46 t7 oc11# / gpio47 p1 par e3 pciclk b3 pcirst# r2 peci ac23 pern1 p30 pern2 m30 pern3 k30 pern4 h30 table 6-1. intel ? ich10 ballout by signal name ball name ball # pern5 f30 pern6 / glan_rxn d29 perp1 p29 perp2 m29 perp3 k29 perp4 h29 perp5 f29 perp6 / glan_rxp d30 perr# f5 petn1 r26 petn2 n26 petn3 l26 petn4 j26 petn5 g26 petn6 / glan_txn e26 petp1 r28 petp2 n28 petp3 l28 petp4 j28 petp5 g28 petp6 / glan_txp e28 pirqa# j5 pirqb# e1 pirqc# f1 pirqd# a3 pirqe# / gpio2 k6 pirqf# / gpio3 l7 pirqg# / gpio4 f2 pirqh# / gpio5 g2 plock# h8 pltrst# c14 pme# r3 pwm0 aj21 pwm1 aj22 pwm2 ak22 pwrbtn# t3 pwrok c25 rcin# l3 req0# k7 table 6-1. intel ? ich10 ballout by signal name ball name ball # req1# / gpio50 g13 req2# / gpio52 f13 req3# / gpio54 g8 ri# g19 rsmrst# f22 rtcrst# a25 rtcx1 a21 rtcx2 b21 s4_state# / gpio26 c11 sata_clkn af18 sata_clkp af19 sata0gp / gpio21 ak25 sata0rxn ak17 sata0rxp aj17 sata0txn ak19 sata0txp aj19 sata1gp / gpio19 ae20 sata1rxn aj15 sata1rxp ak15 sata1txn ah16 sata1txp af16 sata2gp / gpio36 ae21 sata2rxn aj13 sata2rxp ak13 sata2txn ah14 sata2txp af14 sata3gp / gpio37 ae22 sata3rxn aj11 sata3rxp ak11 sata3txn af12 sata3txp ah12 sata4gp af22 sata4rxn aj9 sata4rxp ak9 sata4txn af10 sata4txp ah9 sata5gp ad21 sata5rxn aj7 table 6-1. intel ? ich10 ballout by signal name ball name ball # http://www..net/ datasheet pdf - http://www..net/ 248 datasheet ballout definition sata5rxp ak7 sata5txn af8 sata5txp ah7 sataclkreq# / gpio35 l1 sataled# ae7 satarbias aj6 satarbias# ak6 sclock / gpio22 aj24 sdataout0 / gpio39 ah23 sdataout1 / gpio48 ad20 serirq n6 serr# k5 sload / gpio38 ak24 slp_m# f17 slp_s3# a13 slp_s4# b13 slp_s5# / gpio63 ? g17 smbalert# / gpio11 / jtagtdo ? c16 smbclk h16 smbdata e16 smi# ah26 smlink0 a15 smlink1 b15 spi_clk g23 spi_cs0# e25 spi_cs1# f23 spi_miso b26 spi_mosi c26 spkr n8 srtcrst# h20 sst c19 stop# f10 stp_cpu# / gpio25 ? b18 stp_pci# / gpio15 c15 stpclk# aj29 table 6-1. intel ? ich10 ballout by signal name ball name ball # sus_stat# / lpcpd / gpio61 ? r1 susclk / gpio62 ? r5 sys_reset# f19 tach0 / gpio17 ah21 tach1 / gpio1 ak21 tach2 / gpio6 ah22 tach3 / gpio7 ak23 thrm# ak26 thrmtrip# ad24 dprstp# ak28 dpslp# ae24 tp3 f20 tp4 e19 tp5 c18 tp6 a16 tp7 b16 trdy# e6 usbp0n ad6 usbp0p ad5 usbp10n w2 usbp10p w3 usbp11n v1 usbp11p v2 usbp1n ae3 usbp1p ae2 usbp2n ad1 usbp2p ad2 usbp3n ab6 usbp3p ab5 usbp4n ac3 usbp4p ac2 usbp5n ab1 usbp5p ab2 usbp6n y6 usbp6p y5 usbp7n aa3 usbp7p aa2 usbp8n y1 table 6-1. intel ? ich10 ballout by signal name ball name ball # usbp8p y2 usbp9n v6 usbp9p v5 usbrbias ag2 usbrbias# ag1 v_cpu_io ah28 v_cpu_io aj30 v5ref a6 v5ref_sus af1 vcc1_1 a24 vcc1_1 b24 vcc1_1 c24 vcc1_1 e24 vcc1_1 f24 vcc1_1 g24 vcc1_1 h23 vcc1_1 h24 vcc1_1 j23 vcc1_1 m12 vcc1_1 m13 vcc1_1 m15 vcc1_1 m17 vcc1_1 m18 vcc1_1 m19 vcc1_1 n12 vcc1_1 n19 vcc1_1 r12 vcc1_1 r19 vcc1_1 u12 vcc1_1 u19 vcc1_1 v12 vcc1_1 v19 vcc1_1 w12 vcc1_1 w13 vcc1_1 w15 vcc1_1 w17 vcc1_1 w18 vcc1_1 w19 vcc1_5_a aa7 table 6-1. intel ? ich10 ballout by signal name ball name ball # http://www..net/ datasheet pdf - http://www..net/ datasheet 249 ballout definition vcc1_5_a aa8 vcc1_5_a ab7 vcc1_5_a ab8 vcc1_5_a ab23 vcc1_5_a ac11 vcc1_5_a ac13 vcc1_5_a ac14 vcc1_5_a ac15 vcc1_5_a ac16 vcc1_5_a ac17 vcc1_5_a ac18 vcc1_5_a ac20 vcc1_5_a ad11 vcc1_5_a ad12 vcc1_5_a ad13 vcc1_5_a ad17 vcc1_5_a ae11 vcc1_5_a ae17 vcc1_5_a af11 vcc1_5_a af17 vcc1_5_a ah10 vcc1_5_a ah11 vcc1_5_a ah17 vcc1_5_a ah18 vcc1_5_a aj10 vcc1_5_a aj18 vcc1_5_a ak10 vcc1_5_a ak18 vcc1_5_a h10 vcc1_5_a h11 vcc1_5_a t1 vcc1_5_b aa23 vcc1_5_b aa24 vcc1_5_b aa25 vcc1_5_b ab24 vcc1_5_b ab25 vcc1_5_b ac25 vcc1_5_b ad25 vcc1_5_b ad26 table 6-1. intel ? ich10 ballout by signal name ball name ball # vcc1_5_b ad28 vcc1_5_b ae28 vcc1_5_b ae29 vcc1_5_b ae30 vcc1_5_b j24 vcc1_5_b j25 vcc1_5_b k23 vcc1_5_b k24 vcc1_5_b k25 vcc1_5_b l24 vcc1_5_b l25 vcc1_5_b m23 vcc1_5_b m24 vcc1_5_b m25 vcc1_5_b n24 vcc1_5_b n25 vcc1_5_b p23 vcc1_5_b p24 vcc1_5_b p25 vcc1_5_b r24 vcc1_5_b r25 vcc1_5_b t23 vcc1_5_b t24 vcc1_5_b t25 vcc1_5_b t26 vcc1_5_b t28 vcc1_5_b u24 vcc1_5_b u28 vcc1_5_b u29 vcc1_5_b u30 vcc1_5_b v23 vcc1_5_b v24 vcc1_5_b v25 vcc1_5_b w24 vcc1_5_b w25 vcc1_5_b y23 vcc1_5_b y24 vcc1_5_b y25 vcc3_3 ac19 table 6-1. intel ? ich10 ballout by signal name ball name ball # vcc3_3 ac21 vcc3_3 ad10 vcc3_3 af21 vcc3_3 ah24 vcc3_3 ah30 vcc3_3 ak4 vcc3_3 a2 vcc3_3 b1 vcc3_3 b9 vcc3_3 g3 vcc3_3 g11 vcc3_3 h7 vcc3_3 j2 vcc3_3 k8 vcc3_3 l8 vcccl1_1 a23 vcccl1_5 a26 vcccl3_3 b23 vcccl3_3 c23 vccdmi ag29 vccdmi ag30 vccdmipll t30 vccglan1_5 b30 vccglan1_5 c28 vccglan1_5 c29 vccglan1_5 c30 vccglan3_3 a27 vccglanpll a28 vcchda ac10 vcclan1_1 a10 vcclan1_1 b10 vcclan3_3 a12 vcclan3_3 b12 vccrtc a22 vccsatapll ak20 vccsus1_1 ac7 vccsus1_1 h17 vccsus1_5 ad8 vccsus1_5 h18 table 6-1. intel ? ich10 ballout by signal name ball name ball # http://www..net/ datasheet pdf - http://www..net/ 250 datasheet ballout definition vccsus3_3 af2 vccsus3_3 a17 vccsus3_3 b20 vccsus3_3 c20 vccsus3_3 e17 vccsus3_3 h15 vccsus3_3 u1 vccsus3_3 u2 vccsus3_3 u3 vccsus3_3 u5 vccsus3_3 u6 vccsus3_3 u7 vccsus3_3 u8 vccsus3_3 v8 vccsus3_3 w7 vccsus3_3 w8 vccsus3_3 y8 vccsushda ac9 vccusbpll ak5 vrmpwrgd c22 vss aa1 vss aa5 vss aa6 vss aa29 vss aa30 vss ab3 vss ab26 vss ab28 vss ac1 vss ac5 vss ac6 vss ac8 vss ac12 vss ac24 vss ac29 vss ac30 vss ad3 vss ad7 vss ad9 table 6-1. intel ? ich10 ballout by signal name ball name ball # vss ad14 vss ad15 vss ad16 vss ad18 vss ad19 vss ad22 vss ae1 vss ae5 vss ae6 vss ae8 vss ae9 vss ae10 vss ae12 vss ae13 vss ae14 vss ae15 vss ae16 vss ae18 vss ae19 vss ae25 vss af3 vss af7 vss af9 vss af13 vss af15 vss af20 vss af23 vss af25 vss af29 vss ag28 vss ah2 vss ah6 vss ah8 vss ah13 vss ah15 vss ah19 vss ah20 vss ah29 vss aj4 table 6-1. intel ? ich10 ballout by signal name ball name ball # vss aj5 vss aj8 vss aj12 vss aj14 vss aj16 vss aj20 vss aj23 vss aj26 vss ak2 vss ak8 vss ak12 vss ak14 vss ak16 vss ak27 vss ak29 vss ak30 vss a1 vss a30 vss b2 vss b5 vss b8 vss b11 vss b14 vss b17 vss b19 vss b22 vss b25 vss b27 vss b28 vss d28 vss e2 vss e15 vss e18 vss e22 vss e29 vss e30 vss f6 vss f9 vss f12 table 6-1. intel ? ich10 ballout by signal name ball name ball # http://www..net/ datasheet pdf - http://www..net/ datasheet 251 ballout definition vss f21 vss f26 vss f28 vss g16 vss g25 vss g29 vss g30 vss h2 vss h9 vss h13 vss h19 vss h22 vss h25 vss h26 vss h28 vss j6 vss j29 vss j30 vss k26 vss k28 vss l2 vss l23 vss l29 vss l30 vss m6 vss m8 vss m14 vss m16 vss m26 vss m28 vss n13 vss n14 vss n15 vss n16 vss n17 vss n18 vss n23 vss n29 vss n30 table 6-1. intel ? ich10 ballout by signal name ball name ball # vss p2 vss p6 vss p12 vss p13 vss p14 vss p15 vss p16 vss p17 vss p18 vss p19 vss p26 vss p28 vss r8 vss r13 vss r14 vss r15 vss r16 vss r17 vss r18 vss r23 vss r29 vss r30 vss t2 vss t5 vss t12 vss t13 vss t14 vss t15 vss t16 vss t17 vss t18 vss t19 vss t29 vss u13 vss u14 vss u15 vss u16 vss u17 vss u18 table 6-1. intel ? ich10 ballout by signal name ball name ball # vss u23 vss v3 vss v7 vss v13 vss v14 vss v15 vss v16 vss v17 vss v18 vss v26 vss v28 vss w1 vss w5 vss w6 vss w14 vss w16 vss w23 vss w29 vss w30 vss y3 vss y7 vss y26 vss y28 wake# e20 table 6-1. intel ? ich10 ballout by signal name ball name ball # http://www..net/ datasheet pdf - http://www..net/ ballout definition 252 datasheet http://www..net/ datasheet pdf - http://www..net/ datasheet 253 package information 7 package information 7.1 intel ? ich10 package the ich10 package information is shown in figure 7-1 , figure 7-2 , and figure 7-3 . note: all dimensions, unless otherwise specified, are in millimeters. figure 7-1. intel ? ich10 package (top view) top view pin #1 i.d (shiny) 1.0 dia x 0.15 depth 9.0 x 9.0 from center line 0.127 a // a 0.127 -a- -b- 22.10 ref 4 x 45 http://www..net/ datasheet pdf - http://www..net/ package information 254 datasheet figure 7-2. intel ? ich10 package (bottom view) figure 7-3. intel ? ich10 package (side view) side view -c- c // 0.20 0.15 3 seating plane http://www..net/ datasheet pdf - http://www..net/ datasheet 255 electrical characteristics 8 electrical characteristics this chapter contains the dc and ac characte ristics for the ich10. ac timing diagrams are included. 8.1 thermal specifications refer to the intel ? i/o controller hub (ich10) thermal design guidelines document for ich10 thermal information. 8.2 absolute maximum ratings 8.3 dc characteristics table 8-1. intel ? ich10 absolute maximum ratings parameter maximum limits voltage on any 3.3 v pin with respec t to ground -0.5 to vcc3_3 + 0.5 v voltage on any 5 v tolerant pin with respect to ground (v5ref = 5 v) -0.5 to v5ref + 0.5 v 1.1 v supply voltage with respect to vss -0.5 to 2.1 v 1.25 v supply voltage with respect to vss -0.5v to 2.1v 1.5 v supply voltage with respect to vss -0.5 to 2.1 v 3.3 v supply voltage with respect to vss -0.5 to 4.6 v 5.0 v supply voltage with respect to vss -0.5 to 5.5 v v_cpu_io supply voltage with respect to vss -0.5 to 2.1 v table 8-2. dc current char acteristics (consumer only) 1 power plane maximum power consumption symbol s0 s3 s4/s5 g3 v5ref 2 ma n/a n/a n/a v5ref_sus 2 ma 1 ma 1 ma n/a vcc3_3 308 ma n/a n/a n/a vccsus3_3 212 ma 53 ma 53 ma n/a vcchda 6 32ma n/a n/a n/a vccsushda 6 32 ma 1 ma 1 ma n/a vccglan3_3 1 ma n/a n/a n/a vccglan1_5 80 ma n/a n/a n/a vcclan3_3 5 19 ma 78 ma 78 ma n/a http://www..net/ datasheet pdf - http://www..net/ electrical characteristics 256 datasheet notes: 1. these are estimated dc current numbers. 2. internal voltage regulators power these well s inside the intel ich10 and current for these rails are accounted for in the sourcing voltage rail curre nt requirements. 3. only the g3 state of this rail is show n to provide an estimate of battery life. 4. icc (rtc) data is taken with vccrtc at 3.0 v while the system is in a mechanical off (g3) state at room temperature. 5. the current for this rail in s3 and s4/s5 is based on the integrated lan running at 10/100. 6. the current for this rail was measured with vcchda and vccsushda set to 3.3 v. 7. the current for this rail was me asured with vccdmi set to 1.5 v. vcclan1_1 2, 5 powered by vcc1_1 in s0 powered by vcclan3_3 in s3 powered by vcclan3_3 in s4/ s5 n/a vcccl3_3 19 ma 73 ma 73 ma n/a vcccl1_5 2 powered by vcc1_5_a in s0 powered by vcccl3_3 in s3 powered by vcccl3_3 in s4/s5 n/a vcccl1_12 powered by vcc1_1 in s0 powered by vcccl3_3 in s3 powered by vcccl3_3 in s4/s5 n/a vcc1_5_a 1.644 a n/a n/a n/a vcc1_5_b 646 ma n/a n/a n/a vccsus1_52 powered by vcc1_5_a in s0 powered by vccsus3_3 in s3 powered by vccsus3_3 in s4/s5 n/a vcc1_1 1.634 a n/a n/a n/a vccsus1_12 powered by vcc1_1 in s0 powered by vccsus3_3 in s3 powered by vccsus3_3 in s4/s5 n/a vccrtc 3, 4 n/a n/a n/a 6 a vccdmi 7 50 ma n/a n/a n/a v_cpu_io 2 ma n/a n/a n/a vccglanpll 23 ma n/a n/a n/a vccusbpll 11 ma n/a n/a n/a vccdmipll 7 23 ma n/a n/a n/a vccsatapll 47 ma n/a n/a n/a table 8-2. dc current char acteristics (consumer only) 1 power plane maximum power consumption symbol s0 s3 s4/s5 g3 http://www..net/ datasheet pdf - http://www..net/ datasheet 257 electrical characteristics notes: 1. these are estimated dc current numbers. 2. internal voltage regu lators power these wells inside th e intel ich10 and current for these rails are accounted for in the sourcing voltage rail curre nt requirements. 3. only the g3 state of this rail is show n to provide an estimate of battery life. 4. icc (rtc) data is taken with vccrtc at 3.0 v while the system is in a mechanical off (g3) state at room temperature. 5. the current for this rail in s3 and s4/s5 is based on the integrated lan running at 10/100. 6. the current for this rail was measured with vcchda and vccs ushda set to 3.3 v. 7. the current for this rail was me asured with vccdmi set to 1.5 v. 8. the current for this rail was measured with vcchda and vccs ushda set to 1.5 v. table 8-3. dc current charac teristics (corporate only) power plane maximum power consumption symbol s0 s3 s4/s5 g3 v5ref 1 ma n/a n/a n/a v5ref_sus 2 ma 1 ma 1 ma n/a vcc3_3 273 ma n/a n/a n/a vccsus3_3 212 ma 95 ma 95 ma n/a vcchda 6 30 ma n/a n/a n/a vccsushda 6 31 ma 1 ma 1 ma n/a vcchda 8 10 ma n/a n/a n/a vccsushda 8 11 ma 1 ma 1 ma n/a vccglan3_3 1 ma n/a n/a n/a vccglan1_5 62 ma n/a n/a n/a vcclan3_3 5 17 ma 77 ma 77 ma n/a vcclan1_1 2, 5 powered by vcc1_1 in s0 powered by vcclan3_3 in s3 powered by vcclan3_3 in s3 n/a vcccl3_3 16 ma 70 ma 70 ma n/a vcccl1_5 2 powered by vcc1_5_a in s0 powered by vcccl3_3 in s3 powered by vcccl3_3 in s3 n/a vcccl1_1 2 powered by vcc1_1 in s0 powered by vcccl3_3 in s3 powered by vcccl3_3 in s3 n/a vcc1_5_a 1.390 a n/a n/a n/a vcc1_5_b 591 ma n/a n/a n/a vccsus1_5 2 powered by vcc1_5_a in s0 powered by vccsus3_3 in s3 powered by vccsus3_3 in s3 n/a vcc1_1 2.553 a n/a n/a n/a vccsus1_1 2 powered by vcc1_1 in s0 powered by vccsus3_3 in s3 powered by vccsus3_3 in s3 n/a vccrtc 3, 4 n/a n/a n/a 6 a vccdmi 7 55 ma n/a n/a n/a v_cpu_io 1 ma n/a n/a n/a vccglanpll 23 ma n/a n/a n/a vccusbpll 10 ma n/a n/a n/a vccdmipll 7 22 ma n/a n/a n/a vccsatapll 42 ma n/a n/a n/a http://www..net/ datasheet pdf - http://www..net/ electrical characteristics 258 datasheet table 8-4. dc characteristic input signal association (sheet 1 of 2) symbol associated signals v ih1 /v il1 (5v tolerant) pci signals: ad[31:0], c/be[3:0]#, devsel#, frame#, irdy#, par, perr#, plock#, req[3:0]#, serr#, stop#, trdy# interrupt signals: pirq[d:a]#, pirq[h:e]# gpio signals: gpio[54, 52, 50, 5:2] v ih2 /v il2 gigabit lan connect signals: glan_rx[p,n] v ih3 /v il3 clock signals: clk48 power management signals: mch_sync#, thrm#, vrmpwrgd, lan_rst#, clpwrok sata signals: satagp[5:4, 1:0]satagp[3:2] interrupt signals: serirq processor signals: rcin#, a20gate usb signals: oc[11:0]# gpio signals: gpio[59, 55, 53, 51, 49:36, 35, 31:29, 22:16, 7:6, 1, 0], gpio32 intel ? quiet system technology signals : tach[3:0] strap signals: gnt[3:0]#,spkr, sataled# (strap purposes only) v ih4 /v il4 clock signals: clk14, pciclk lpc/firmware hub signals: lad[3:0]/fwh[3:0], ldrq0#, ldrq1# pci signals: pme# spi signals: spi_miso gpio signals: gpio[33, 23] strap signals: spi_mosi, gnt0# (strap purposes only) v ih5 /v il5 smbus signals: smbclk, smbdata, smbalert# system management signals: smlink[1:0], linkalert# gpio signals : gpio[60, 11] v ih6 /v il6 lan signals: glan_clk, lan_rxd[2:0] v ih7 /v il7 processor signals: ferr#, thrmtrip# v imin8 /v imax8 pci express* data rx signals: per[p,n][6:1] v ih9 /v il9 real time clock signals: rtcx1 v imin10 /v imax10 sata signals: sata[3:0]rx[p,n], sata[5:4]rx[p,n] v ih11 /v il11 intel ? high definition audio signals: hda_sdin[3:0] strap signals: hda_sdout, hda_sync (strap purposes only) gpio signals : gpio34 note: see v il_hda /v ih_hda for high definition audio low voltage mode v ih12 /v il12 / v cross(abs) clock signals: dmi_clkn, dmi_clkp, sata_clkn, sata_clkp v ih13 /v il13 power management signals: pwrbtn#, ri#, sys_reset#, wake# gpio signals: gpio[60, 57:56, 28:26, 24, 14:12, 10:8], gpio[25, 15] v ih14 /v il14 power management signals: pwrok, rsmrst# system management signals: intruder# miscellaneous signals: intvrmen, lan100_slp, rtcrst#, srtcrst# http://www..net/ datasheet pdf - http://www..net/ datasheet 259 electrical characteristics 1. v di = | usbpx[p] ? usbpx[n] 2. includes vdi range 3. applies to low-speed/high-speed usb 4. pci express mvdiff p-p = 2*|petp[x] ? petn[x]| 5. glan mvdiff p-p = 2* |glan_rxp ? glan_rxn| 6. sata vdiff, rx (vimax10/min10) is measured at the sata connector on the receiver side (generally, the motherboard connector), where sata mvdiff p-p = 2*|sata[x]rxp ? sata[x]rxn| 7. vccrtc is the voltage applied to the vccrtc well of the ich10. when the system is in a g3 state, this is generally supplied by the coin cell battery, but for s5 and greater, this is generally vccsus3_3. 8. cl_vref = 0.27 (vcccl1_5). cl_vref0 applies to all configurations. 9. applies to ultra dma modes greater th an ultra dma mode 4. 10. this is an ac characteri stic that represents transi ent values for these signals. 11. applies to hogh-speed usb 2.0. v ih_cl /v il_cl controller link: cl_clk0, cl_data0 v di / v cm / v se (5 v tolerant) usb signals: usbp[11:0][p,n] (low-speed and full-speed) v hssq / v hsdsc / v hscm (5 v tolerant) usb signals: usbp[11:0][p,n] (in high-speed mode) v ih_hda / v il_hda intel ? high definition audio signals: hda_sdin[3:0] strap signals: hda_sdout, hda_sync (strap purposes only) note: only applies when running in low voltage mode (1.5 v) v ih_sst /v il_sst intel ? quiet system technology signals: sst v ih_peci /v il_peci intel ? quiet system technology signals: peci table 8-4. dc characteri stic input signal association (sheet 2 of 2) symbol associated signals http://www..net/ datasheet pdf - http://www..net/ electrical characteristics 260 datasheet table 8-5. dc input charac teristics (she et 1 of 2) symbol parameter min max unit notes v il1 input low voltage ?0.5 0.3(vcc3_3) v v ih1 input high voltage 0.5(vcc3_3) v5ref + 0.5 v v il2 minimum input voltage 200 ? mvdiff p-p note 5 v ih2 maximum input voltage ? 1350 mvdiff p-p note 5 v il3 input low voltage ?0.5 0.8 v v ih3 input high voltage 2.0 3.3 v + 0.5 v note 12 v il4 input low voltage ?0.5 0.3(3.3 v) v note 12 v ih4 input high voltage 0.5(3.3 v) 3.3 v + 0.5 v note 12 v il5 input low voltage ?0.5 0.8 v v ih5 input high voltage 2.1 3.3 v + 0.5 v note 12 v il6 input low voltage -0.5 0.3(3.3 v) v note 12 v ih6 input high voltage 0.6(3.3 v) 3.3 v + 0.5 v note 12 v il7 input low voltage ?0.5 0.58(v_cpu_io) v v ih7 input high voltage 0.73(v_cpu_io) v_cpu_io + 0.5 v v imin8 minimum input voltage 175 ? mvdiff p-p note 4 v imax8 maximum input voltage ? 1200 mvdiff p-p note 4 v il9 input low voltage ?0.5 0.10 v v ih9 input high voltage 0.40 1.2 v v imin10- gen1i minimum input voltage - 1.5 gb/s internal sata 325 ? mvdiff p-p 6 v imax10-gen1i maximum input voltage - 1.5 gb/s internal sata ? 600 mvdiff p-p 6 v imin10-gen1m minimum input voltage - 1.5 gb/s esata 240 ? mvdiff p-p 6 v imax10-gen1m maximum input voltage - 1.5 gb/s esata ? 600 mvdiff p-p 6 v imin10-gen2i minimum input voltage - 3.0 gb/s internal sata 275 ? mvdiff p-p 6 v imax10-gen2i maximum input voltage - 3.0 gb/s internal sata ? 750 mvdiff p-p 6 v imin10-gen2m minimum input voltage - 3.0 gb/s esata 240 ? mvdiff p-p 6 http://www..net/ datasheet pdf - http://www..net/ datasheet 261 electrical characteristics notes: 1. v di = | usbpx[p] ? usbpx[n] 2. includes vdi range 3. applies to low-sp eed/full-speed usb 4. pci express mvdiff p-p = 2*|petp[x] - petn[x]| 5. glan mvdiff p-p = 2* |glan_rxp - glan_rxn| 6. sata vdiff, rx (vimax10/min10) is measured at the sata connector on the receiver side (generally, the motherboard connector), wh ere sata mvdiff p-p = 2*|sata[x]rxp - sata[x]rxn| v imax10-gen2m maximum input voltage - 3.0 gb/s esata ? 750 mvdiff p-p 6 v il11 input low voltage ? 0.5 0.35( 3.3 v )v note 12 v ih11 input high voltage 0.65( 3.3 v ) 3.3 v + 0.5 v note 12 v il12 input low voltage -0.150 0.150 v v ih12 input high voltage 0.660 0.850 v v il13 input low voltage ? 0.5 0.8 v v ih13 input high voltage 2.0 3.3 v + 0.5 v note 12 v il14 input low voltage ? 0.5 0.78 v v ih14 input high voltage 2.0 vccrtc + 0.5 v note 7 v il_cl input low voltage ? 0.3 (cl_vref - 0.0 7 5) v note 8 v ih_cl input high voltage (cl_vref + 0.0 7 5) 1.2 v note 8 v il_cl2 input low voltage ? 0.5 0.3(vcccl3_3) v v ih_cl2 input high voltage 0.5(vcccl3_3) vcccl3_3 + 0.5 v v cross(abs) absolute crossing point 0.250 0.550 v v di differential input sensitivity 0.2 ? v note 1,3 v cm differential common mode range 0.8 2.5 v note 2,3 v se single-ended receiver threshold 0.8 2.0 v note 3 v hssq hs squelch detection threshold 100 150 mv note 11 v hsdsc hs disconnect detection threshold 525 625 mv note 11 v hscm hs data signaling common mode voltage range ?50 500 mv note 11 v il_hda input low voltage ? 0.4(vcc_hda) v v ih_hda input high voltage 0.6(vcc_hda) ? v v il_sst input low voltage -0.5 0.4 v v ih_sst input high voltage 1.1 vcc + 0.5 v v il_peci input low voltage -0.5 0.275(v_cpu_io) v v ih_peci input high voltage 0.725(v_cpu_io) v_cpu_io + 0.5 v table 8-5. dc input charac teristics (sheet 2 of 2) symbol parameter min max unit notes http://www..net/ datasheet pdf - http://www..net/ electrical characteristics 262 datasheet 7. vccrtc is the voltage applied to the vccrtc well of the ich10. when the system is in a g3 state, this is generally supplie d by the coin cell battery, but for s5 and greater, this is generally vccsus3_3. 8. cl_vref = 0.27 (vcccl1_5). cl_vref0 applies to all configurations. 9. applies to ultra dma modes greater th an ultra dma mode 4 10. this is an ac characteristic that repr esents transient values for these signals 11. applies to hogh-speed usb 2.0. 12. 3.3 v refers to vccsus3_3 for signals in the suspend well and to vcc3_3 for signals in the core well. see ta b l e 3 - 2 or ta b l e 3 - 3 for signal and power well association. table 8-6. dc characteristic output signal association (sheet 1 of 2) symbol associated signals v oh1 /v ol1 processor signals: a20m#, ignne#, init#, intr, nmi, smi#, stpclk#, cpupwrgd, dpslp# power management signals: dprstp# v oh2 /v ol2 pci signals: ad[31:0], c/be[3:0]#, devsel#, frame#, irdy#, par, perr#, plock#, serr# (1) , stop#, trdy# intel ? high definition audio signals: hda_rst#, hda_sdout, hda_sync, hda_bit_clk note: see v oh_hda /v ol_hda for high definition audio low voltage mode gpio signals: gpio33 v oh3 /v ol3 smbus signals: smbclk (1) , smbdata (1) system management signals: smlink[1:0] (1) , linkalert# gpio signals: gpio[60, 11] v oh4 /v ol4 power management signals: slp_s3#, slp_s4#, slp_s5#, slp_m#, susclk, sus_stat#/lpcpd#, ck _pwrgd, s4_state#, dprslpvr sata signals : sataclkreq#, sataled#, sload, sdataout[1:0] gpio signals: gpio[49:48, 39:35, 32:31, 26, 21:18, 16, 7:6, 0], gpio32 other signals: spkr interrupt signals: serirq v oh5 /v ol5 usb signals : usbp[11:0][p,n] in low-speed and full-speed modes v omin6 /v omax6 pci express* data tx signals: pet[p,n][6:1] v omin7 /v omax7 sata signals: sata[5:4, 1:0]tx[p,n], sata[3:2]tx[p,n] v oh8 /v ol8 lpc/firmware hub signals: lad[3:0]/fwh[3:0], lframe#/fwh[4], init3_3v# power management signal: pltrst# pci signals: pcirst#, gnt[3:0]#, pme# (1) interrupt signals: pirq[d:a], pirq[h:e]# (1) gpio signals: gpio[58, 55:50, 34, 23:22, 17, 5:2, 1] sata signals: sclock spi signals: spi_cs0#, spi_cs1#, spi_mosi, spi_clk lan signals: lan_rstsync, lan_txd[2:0] http://www..net/ datasheet pdf - http://www..net/ datasheet 263 electrical characteristics note: 1. these signals are open-drain. v oh9 /v ol9 power management signals: stp_cpu#, stp_pci# gpio signals: gpio[60, 59, 57:56, 47:40, 31:27, 24, 15:12, 10:8], gpio[25, 15] system management signals: linkalert#, v omin10 /v omax10 gigabit lan connect signals: glan_tx[p,n] v hsoi v hsoh v hsol v chirpj v chirpk usb signals: usbp[11:0][p:n] in high-speed mode v oh_hda /v ol_hda intel ? high definition audio signals: hda_rst#, hda_sdout, hda_sync note: only applies when running in low voltage mode (1.5 v) v oh_pwm / v ol_pwm intel ? quiet system technology pwm: pwm[2:0] (1) v oh_cl1 /v ol_cl1 link controller signals: cl_clk0, cl_data0 v oh_cl2 /v ol_cl2 link controller signals: cl_rst0# v oh_sst /v ol_sst sst signal: sst v oh_peci / v ol_peci peci signal: peci table 8-6. dc characteri stic output signal assoc iation (sheet 2 of 2) symbol associated signals http://www..net/ datasheet pdf - http://www..net/ electrical characteristics 264 datasheet table 8-7. dc output characteristics (sheet 1 of 2) symbol parameter min max unit i ol / i oh notes v ol1 output low voltage ? 0.255 v 3 ma note 4 v oh1 output high voltage v_cpu_io - 0.3 ? v -3 ma v ol2 output low voltage ? 0.1(3.3 v) v 1.5 ma note 7 v oh2 output high voltage 0.9(3.3 v) ? v -0.5 ma note 7 v ol3 output low voltage ? 0.4 v 4 ma v oh3 output high voltage 3.3 v - 0.5 ? v -2 ma note 1 v ol4 output low voltage ? 0.4 v 6 ma v oh4 output high voltage 3.3 v - 0.5 ? v -2 ma note 7 v ol5 output low voltage ? 0.4 v 5 ma v oh5 output high voltage 3.3 v ? 0.5 ? v -2 ma note 7 v omin6 minimum output voltage 800 ? mvdif fp-p note 2 v omax6 maximum output voltage ? 1200 mvdif fp-p note 2 v omin7-gen1i,m minimum output voltage 400 ? mvdif fp-p note 3 v omax7-gen1i,m maximum output voltage ? 600 mvdif fp-p note 3 v omin7-gen2i,m minimum output voltage 400 ? mvdif fp-p note 3 v omax7-gen2i,m maximum output voltage ? 700 mvdif fp-p note 3 v ol8 output low voltage ? 0.1(3.3 v) v 1.5 ma note 7 v oh8 output high voltage 0.9(3.3 v) ? v -0.5 ma note 1, 7 v ol9 output low voltage ? 0.4 v 6 ma v oh9 output high voltage 3.3 v - 0.5 ? v -0.5 ma note 7 v omin10 minimum output voltage 750 ? mvdif fp-p note 6 v omax10 maximum output voltage ? 1350 mvdif fp-p note 6 v hsoi hs idle level ?10.0 10.0 mv v hsoh hs data signaling high 360 440 mv v hsol hs data signaling low ?10.0 10.0 mv v chirpj chirp j level 700 1100 mv v chirpk chirp k level ?900 ?500 mv http://www..net/ datasheet pdf - http://www..net/ datasheet 265 electrical characteristics notes: 1. the serr#, pirq[h:a], smbdata, smbclk , linkalert#, smlink[1:0], and pwm[2:0] signal has an open-drain driver and satale d# has an open-collector driver, and the v oh specification does not apply. this signal must have external pull up resistor. 2. pci express mvdiff p-p = 2*|petp[x] ? petn[x]| 3. sata vdiff, tx (v omin7 /v omax7 ) is measured at the sata co nnector on the transmit side (generally, the motherboard connector), wh ere sata mvdiff p-p = 2*|sata[x]txp ? sata[x]txn| 4. maximum iol for cpupwrgd is 12 ma for sh ort durations (<500 ms per 1.5 s) and 9 ma for long durations. 5. for init3_3v only, for low current devices, the following applies: v ol5 max is 0.15 v at an i ol5 of 2 ma. 6. glan mvdiff p-p = 2*|glan_txp ? glan_txn| 7. 3.3 v refers to vccsus3_3 for signals in the suspend well and to vcc3_3 for signals in the core well. see ta b l e 3 - 2 or ta b l e 3 - 3 for signal and powe r well association. v ol_pwm output low voltage ? 0.4 v 5 ma v oh_pwm output high voltage ? ? note 1 v ol_cl1 output low voltage ? 0.15 v 1 ma v oh_cl1 output high voltage 0.485(vcccl1_5) ? v v ol_cl2 output low voltage ? 0.1(vcccl1_5) v 1.5 ma v oh_cl2 output high voltage 0.9(vcccl1_5) ? v -1.5 ma v ol_cl3 output low voltage ? 0.4 v 6 ma v oh_cl3 output high voltage vcccl3_3 -0.5 ? v -0.5 ma v ol_sst output low voltage ? 0.3 v 0.5 ma v oh_sst output high voltage 1.1 ? v -6 ma v ol_peci output low voltage ? 0.25(v_cpu_io) v 0.5 ma v oh_peci output high voltage 0.75(v_cpu_io) ? -6 ma vol_hda output low voltage ? 0.1(vcchda) v 1.5 ma voh_hda output high volt age 0.9(vcchda) ? v -0.5 ma table 8-7. dc output charac teristics (sheet 2 of 2) symbol parameter min max unit i ol / i oh notes http://www..net/ datasheet pdf - http://www..net/ electrical characteristics 266 datasheet table 8-8. other dc charac teristics (s heet 1 of 2) symbol parameter min nom max unit notes v_cpu_io processor i/f 0.945 ? 1.3 v 1 v5ref ich10 core well reference voltage 4.75 5 5.25 v 1 cl_vref controller link reference voltage 0.385 0.405 0.425 v 1, 3 vcc3_3 i/o buffer voltage 3.135 3.3 3.465 v 1 vcc1_5_a, vcc1_5_b, vccusbpll, vccsatapll, vccdmipll vccglanpll internal logic and i/o buffer voltage 1.425 1.5 1.575 v 1 v5ref_sus suspend well reference voltage 4.75 5 5.25 v 1 vccsus3_3 suspend well i/o buffer voltage 3.135 3.3 3.465 v 1 vcc1_1 (consumer only) internal logic voltage 0.998 1.1 1.155 v 1 vcc1_1 (corporate only) internal logic voltage 1.045 1.1 1.155 v 1 vcchda high definition audio controller core voltage 3.135 3.3 3.465 v 1 vcchda (low voltage 1.5 v) high definition audio controller low voltage mode core voltage 1.425 1.5 1.575 v 1 vcc_dmi dmi buffer voltage 1.188 1.25 1.312 v vcc_dmi (esi mode only) dmi buffer voltage 1.425 1.5 1.575 v vcclan3_3 lan controller i/o buffer voltage 3.135 3.3 3.465 v 1 vccglan1_5 gigabit lan transmit ter and receiver voltage 1.425 1.5 1.575 v 1 vccglan3_3 gigabit lan internal logic and i/o buffer voltage 3.135 3.3 3.465 v 1 vcccl3_3 controller link buffer voltage 3.135 ? 3.465 v 1 vccrtc (g3-s0) battery voltage 2 ? 3.465 v 1 vccsushda high definition audio controller suspend voltage 3.135 3.3 3.465 v 1 vccsushda (low voltage) high definition audio controller low voltage mode suspend voltage 1.425 1.5 1.575 v 1 v di differential input sensitivity 0.2 ? ? v |(usbpx+,usb px?)| v cm differential common mode range 0.8 ? 2.5 v includes v di v crs output signal crossover voltage 1.3 ? 2.0 v v se single ended rcvr threshold 0.8 ? 2.0 v i li1 ata input leakage current ?200 ? 200 a (0 v < v in < 5v) http://www..net/ datasheet pdf - http://www..net/ datasheet 267 electrical characteristics notes: 1. the i/o buffer supply voltage is measured at the ich package pins. the tolerances shown in ta b l e 8 - 8 are inclusive of all noise from dc up to 20 mhz. in testing, the voltage rails should be measured with a band width limited os cilloscope that has a rolloff of 3 db/decade above 20 mhz. 2. includes clk14, clk48, glan_clk and pciclk 3. cl_vref voltage applies when pin is driven by external circuit. i li2 pci_3v hi-z state data line leakage ?10 ? 10 a (0 v < vin < vcc3_3) i li3 pci_5v hi-z state data line leakage ?70 ? 70 a max v in = 2.7 v min v in = 0.5 v i li4 input leakage current ? cl ock signals ?100 ? +100 a 2 c in input capacitance ? all other ? ? 12 pf f c = 1 mhz c out output capacitance ? ? 12 pf f c = 1 mhz c i/o i/o capacitance ? ? 12 pf f c = 1 mhz typical value c l xtal1 6 pf c l xtal2 6 pf table 8-8. other dc characteristics (sheet 2 of 2) symbol parameter min nom max unit notes http://www..net/ datasheet pdf - http://www..net/ electrical characteristics 268 datasheet 8.4 ac characteristics 1 table 8-9. clock timings (sheet 1 of 2) sym parameter min max unit notes figure pci clock (pciclk) t1 period 30 33.3 ns 8-1 t2 high time 12 ? ns 8-1 t3 low time 12 ? ns 8-1 t4 rise time ? 3 ns 8-1 t5 fall time ? 3 ns 8-1 14 mhz clock (clk14) t6 period 67 70 ns 8-1 t7 high time 20 ? ns 8-1 t8 low time 20 ? ns 8-1 t41 rising edge rate 1.0 4.0 v/ns 5 t42 falling edge rate 1.0 4.0 v/ns 5 48 mhz clock (clk48) f clk48 operating frequency 48.000 ? mhz 1 t9 frequency tolerance ? 100 ppm t10 high time 7 ? ns 8-1 t11 low time 7 ? ns 8-1 t12 rise time ? 1.2 ns 8-1 t13 fall time ? 1.2 ns 8-1 smbus clock (smbclk) f smb operating frequency 10 100 khz t18 high time 4.0 50 s2 8-10 t19 low time 4.7 ? s 8-10 t20 rise time ? 1000 ns 8-10 t21 fall time ? 300 ns 8-10 hda_bit_clk (intel ? high definition audio) f hda operating frequency 24.0 mhz frequency tolerance ? 100 ppm t26a input jitter (refer to clock chip specification) ? 300 ppm t27a high time (measured at 0.75 vcc) 18.75 22.91 ns 8-1 t28a low time (measured at 0.35 vcc) 18.75 22.91 ns 8-1 sata clock (sata_clkp, sata_clkn) / dmi clock (dmi_clkp, dmi_clkn) t36 period 9.997 10.0533 ns http://www..net/ datasheet pdf - http://www..net/ datasheet 269 electrical characteristics notes: 1. the clk48 expects a 40/60% duty cycle. 2. the maximum high time (t18 max) provide a simple ensured method for devices to detect bus idle conditions. 3. bitclk rise and fall times are measured from 10%vdd and 90%vdd. 4. susclk duty cycle can range from 30% minimum to 70% maximum. 5. clk14 edge rates in a system as measured from 0.8 v to 2.0 v. 6. the active frequency can be 5 mhz, 50 mhz or 62.5 mhz depe nding on the interface speed. dynamic changes of the normal op erating frequency are not allowed. 7. see ck505 clock synthesizer specification for measurement procedure. tsatasl slew rate 1 8 v/ns 7 suspend clock (susclk) f susclk operating frequency 32 khz 4 t39 high time 10 ? s4 t39a low time 10 ? s4 gigabit internet clock (glan_clk) tglanclk operating fequency 5 62.5 mhz 6 tglanhi high time 6.4 ? ns tglanlo low time 6.4 ? ns tglansl slew rate 1.0 4 v/ns intel ? quiet system technology f pwm pwm operating frequency 10 28,000 hz table 8-9. clock timings (sheet 2 of 2) sym parameter min max unit notes figure table 8-10. pci interface timing sym parameter min max units notes figure t40 ad[31:0] valid delay 2 11 ns 1 8-2 t41 ad[31:0] setup time to pciclk rising 7 ? ns 8-3 t42 ad[31:0] hold time from pciclk rising 0 ? ns 8-3 t43 c/be[3:0]#, frame#, trdy#, irdy#, stop#, par, perr#, plock#, devsel# valid delay from pciclk rising 211ns 1 8-2 t44 c/be[3:0]#, frame#, trdy#, irdy#, stop#, par, perr#, plock#, idsel, devsel# output enable delay from pciclk rising 2ns 8-6 t45 c/be[3:0]#, frame#, trdy#, irdy#, stop#, perr#, plock#, devsel#, gnt[a:b]# float delay from pciclk rising 228ns 8-4 t46 c/be[3:0]#, frame#, trdy#, irdy#, stop#, serr#, perr#, devsel#, setup time to pciclk rising 7ns 8-3 http://www..net/ datasheet pdf - http://www..net/ electrical characteristics 270 datasheet note: 1. refer to note 3 of table 4-4 in section 4.2.2.2 and note 2 of table 4-6 in section 4.2.3.2 of the pci local bus specification, revision 2.3 for measurement details. t47 c/be[3:0]#, frame#, trdy#, irdy#, stop#, serr#, perr#, devsel#, req[a:b]# hold time from pclkin rising 0?ns 8-3 t48 pcirst# low pulse width 1 ms 8-5 t49 gnt[3:0]# valid delay from pciclk rising 212ns t50 req[3:0]# setup time to pciclk rising 12 ? ns table 8-10. pci interface timing sym parameter min max units notes figure table 8-11. universal serial bus timing sym parameter min max units notes fig full-speed source (note 7) t100 usbpx+, usbpx- driver rise time 4 20 ns 1, c l = 50 pf 8-7 t101 usbpx+, usbpx- driver fall time 4 20 ns 1, c l = 50 pf 8-7 t102 source differential driver jitter - to next transition - for paired transitions ?3.5 ?4 3.5 4 ns ns 2, 3 8-8 t103 source se0 interval of eop 160 175 ns 4 8-9 t104 source jitter for differential tran sit ion to se0 transi ti on ?2 5 ns 5 t105 receiver data jitter tolerance - t o next transition - for paired transitions ?18.5 ?9 18.5 9 ns ns 3 8-8 t106 eop width: must accept as eop 82 ? ns 4 8-9 t107 width of se0 interval during differential transition ?14 ns low-speed source (note 8) t108 usbpx+, usbpx ? driver rise time 75 300 ns 1, 6 c l = 50 pf c l = 350 pf 8-7 t109 usbpx+, usbpx ? driver fall time 75 300 ns 1,6 c l = 50 pf c l = 350 pf 8-7 t110 source differential driver jitter to n e x t tra n s i t i o n for paired transitions ?25 ?14 25 14 ns ns 2, 3 8-8 t111 source se0 interval of eop 1.25 1.50 s 4 8-9 t112 source jitter for differential tran sit ion to se0 transi ti on ?40 100 ns 5 http://www..net/ datasheet pdf - http://www..net/ datasheet 271 electrical characteristics notes: 1. driver output resistance under steady state drive is spec?d at 28 ohms at minimum and 43 ohms at maximum. 2. timing difference between th e differential data signals. 3. measured at crossover point of differential data signals. 4. measured at 50% swing point of data signals. 5. measured from last crossover point to 50% swin g point of data line at leading edge of eop. 6. measured from 10% to 90% of the data signal. 7. full-speed data rate has minimum of 11.97 mb/s and maximum of 12.03 mb/s. 8. low-speed data rate has a minimum of 1.48 mb/s and a maximum of 1.52 mb/s. notes: 1. 20% ? 80% at transmitter 2. 80% ? 20% at transmitter 3. as measured from 100 mv differential cros spoints of last and first edges of burst. 4. operating data period during out-of-band burs t transmissions. t113 receiver data jitter tolerance - to next transition- for paired tra nsi ti ons ?152 ?200 152 200 ns ns 3 8-8 t114 eop width: must accept as eop 670 ? ns 4 8-9 t115 width of se0 interval during differential transition ? 210 ns table 8-11. universal serial bus timing sym parameter min max units notes fig full-speed source (note 7) table 8-12. sata interface timings sym parameter min max units notes figure ui gen i operating data period 666.43 670.23 ps ui-2 gen ii operating data period (3gb/s) 333.21 335.11 ps t120 rise time 0.15 0.41 ui 1 t121 fall time 0.15 0.41 ui 2 t122 tx differential skew ? 20 ps t123 comreset 310.4 329.6 ns 3 t124 comwake transmit spacing 103.5 109.9 ns 3 t125 oob operating data period 646.67 686.67 ns 4 http://www..net/ datasheet pdf - http://www..net/ electrical characteristics 272 datasheet notes: 1. a device will timeout when any clock low exceeds this value. 2. t137 is the cumulative time a slave device is allowed to extend the clock cycles in one message from the initial start to stop. if a slav e device exceeds this time, it is expected to release both its clock and da ta lines and reset itself. 3. t138 is the cumulative time a master device is allowed to extend its clock cycles within each byte of a message as defined from start-to-ack, ack-to-ack or ack-to-stop. 4. t134 has a minimum timing for i 2 c of 0 ns, while the minimum timing for smbus is 300 ns. table 8-13. smbus timing sym parameter min max units notes fig t130 bus free time between stop and start condition 4.7 ? s 8-10 t131 hold time after (repeated) start condition. after this period, the first clock is generated. 4.0 ? s 8-10 t132 repeated start condition setup time 4.7 ? s 8-10 t133 stop condition setup time 4.0 ? s 8-10 t134 data hold time 0 ? ns 4 8-10 t135 data setup time 250 ? ns 8-10 t136 device time out 25 35 ms 1 t137 cumulative clock low extend time (slave device) ?25 ms 2 8-11 t138 cumulative clock low extend time (master device) ?10 ms 3 8-11 table 8-14. intel ? high definition audio timing sym parameter min max units notes fig t143 time duration for which hda_sdout is valid before hda_bit_clk edge. 7? ns 8-13 t144 time duration for which hda_sdout is valid after hda_bit_clk edge. 7? ns 8-13 t145 setup time for hda_sdin[3:0] at rising edge of hda_bit_clk 15 ? ns 8-13 t146 hold time for hda_sdin [3:0] at rising edge of hda_bit_clk 0? ns 8-13 http://www..net/ datasheet pdf - http://www..net/ datasheet 273 electrical characteristics 1 note: 1. the typical clock frequency driven by the ich10 is 17.86 mhz. table 8-15. lpc timing sym parameter min max units notes fig t150 lad[3:0] valid delay from pciclk rising 2 11 ns 8-2 t151 lad[3:0] output enable delay from pciclk rising 2ns 8-6 t152 lad[3:0] float delay from pciclk rising ? 28 ns 8-4 t153 lad[3:0] setup time to pciclk rising 7 ? ns 8-3 t154 lad[3:0] hold time from pciclk rising 0 ? ns 8-3 t155 ldrq[1:0]# setup time to pciclk rising 12 ? ns 8-3 t156 ldrq[1:0]# hold time from pciclk rising 0 ? ns 8-3 t157 lframe# valid delay from pciclk rising 2 12 ns 8-2 table 8-16. miscellaneous timings sym parameter min max units notes fig t160 serirq setup time to pciclk rising 7 ? ns 8-3 t161 serirq hold time from pciclk rising 0 ? ns 8-3 t162 ri#, extsmi#, gpio, usb resume pulse width 2 ? rtcclk 8-5 t163 spkr valid delay from osc rising ? 200 ns 8-2 t164 serr# active to nmi active ? 200 ns t165 ignne# inactive from ferr# inactive ? 230 ns table 8-17. spi timings (20 mhz) sym parameter min max units notes fig t180 serial clock frequency - 20m hz operation 17.2 18.4 mhz 1 t182 spi clock duty cycle at the host 40% 60% 8-12 t183 tco of spi_mosi with respect to serial clock falling edge at the host -5 13 ns 8-12 t184 setup of spi_miso with respect to serial clock falling edge at the host 16 ? ns 8-12 t185 hold of spi_miso with respect to serial clock falling edge at the host 0?ns 8-12 t186 setup of spi_cs[1:0]# assertion with respect to serial clock rising at the host 30 ? ns 8-12 t187 hold of spi_cs[1:0]# deassertion with respect to serial clock falling at the host 30 ? ns 8-12 http://www..net/ datasheet pdf - http://www..net/ electrical characteristics 274 datasheet note: 1. the typical clock frequency driven by the ich10 is 31.25 mhz. notes: 1. the originator must drive a mo re restrictive time to allow fo r quantized sampling errors by a client yet still attain the minimum time less than 500 s. t bit limits apply equally to t bit- a and t bit-m . ich10 is targeted on 1 mbps which is 1 s bit time. 2. the minimum and maximum bit times are relative to t bit defined in the timing negotiation pulse. 3. t bit-a is the negotiated address bit time and t bit-m is the negotiated message bit time. table 8-18. spi timings (33 mhz) sym parameter min max units notes fig t180b serial clock frequency - 33 mhz operation 30.3 32.19 mhz 1 t182b spi clock duty cycle at the host 48% 52% 8-12 t183b tco of spi_mosi with respect to serial clock falling e dge at the host -5 5 ns 8-12 t184b setup of spi_miso with respect to serial clock falling e dge at the host 8?ns 8-12 t185b hold of spi_miso with respect to serial clock falling e dge at the host 0?ns 8-12 t186b setup of spi_cs[1:0]# assertion with respect to serial cloc k rising at the host 30 ? ns 8-12 t187b hold of spi_cs[1:0]# deassertion with respect to serial cloc k falling at the host 30 ? ns 8-12 table 8-19. sst timings sym parameter min max units notes fig t bit bit time (overall time evident on sst) bit time driven by an originator 0.495 0.495 500 250 s s 1- t bit, jitter bit time jitter between adjacent bits in an sst message header or data bytes after timing has been negotiated ??% t bit ,drift change in bit time across a sst address or sst message bits as driven by the originator. this limit only applies across t bit-a bit drift and t bit-m drift. ??% t h1 high level time for logic '1' 0.6 0.8 x t bit 2 t h0 high level time for logic '0' 0.2 0.4 x t bit t sstr rise time (measured from v ol = 0.3v to v ih,min ) ?25 + 5 ns/ node t sstf fall time (measured from v oh = 1.1v to v il,max ) ?33 ns/ node http://www..net/ datasheet pdf - http://www..net/ datasheet 275 electrical characteristics notes: 1. the originator must drive a mo re restrictive time to allow fo r quantized sampling errors by a client yet still attain the minimum time less than 500 s. tbit limits apply equally to t bit- a and t bit-m . ich10 is targeted on 2 mhz which is 500 ns bit time. 2. the minimum and maximum bit times are relative to t bit defined in the ti ming negotiation pulse. 3. extended trace lengths may appear as additional nodes. 4. t bit-a is the negotiated a ddress bit time and t bit-m is the negotiated message bit time. table 8-20. peci timings sym parameter min max units notes fig t bit bit time (overall time evident on peci) bit time driven by an originator 0.495 0.495 500 250 s s 1 t bit ,jitter bit time jitter between adjacent bits in an peci message header or data bytes after timing has been negotiated ??% t bit ,drift change in bit time across a peci address or peci message bits as driven by the originator. this limit only applies across t bit-a bit drift and t bit-m drift. ??% t h1 high level time for logic '1' 0.6 0.8 x t bit 2 t h0 high level time for logic '0' 0.2 0.4 x t bit t pecir rise time (measured from vol to vih,min, vtt(nom) -5%) ?30 + 5 ns/ node 3 t pecif fall time (measured from v oh to v il ,max, vtt(nom) +5%) ?30 ns/ node 3 table 8-21. power sequencing and re set signal timings (sheet 1 of 2) sym parameter min max units notes fig t200 vccrtc active to rtcrst# inactive 18 ? ms 8-14 t201 v5ref_sus active to vccsus3_3 active 0?ms1 8-14 t202 vccsus3_3 active to vccsus1_1 active ?? ? 2 8-14 t203 vccrtc supply active to vccsus supplies active 0?ms3, 9 8-14 t204 vccsus supplies active to rsmrst# inactive 10 ? ms 9 8-14 8-15 t209 v5ref active to vcc3_3 active 0 ? ms 1 8-14 t211 vcc1_5 active to v_cpu_io active ? ? ? 4 8-14 t212 vrmpwrgd active to pwrok active 5 ? ms 8-15 8-17 t213 vccsus supplies active to vcc supplies active 0?ms9, 10 8-14 http://www..net/ datasheet pdf - http://www..net/ electrical characteristics 276 datasheet notes: 1. v5ref must be powered up before vcc3_3, or after vcc3_3 within 0.7 v. also, v5ref must power down after vcc3_3, or before vcc3_3 within 0.7 v. 2. the associated 3.3 v and 1.1 v supplies are assumed to power up or down ?together?. 3. the vccsus supplies must never be active while the vc crtc supply is inactive. 4. a) vcc1_5 must power up befo re v_cpu_io or after v_cpu_io within 0.7 v, b) v_cpu_io must power down before vcc1_5 or after vcc1_5 within 0.7 v. 5. init# value determined by value of the cpu bistenable bit (chipset configuration register offset 3414h: bit 2). 6. these transitions are clocked off the intern al rtc. 1 rtc clock is approximately from 28.992 s to 32.044 s 7. ?vccglanpll inactive" is define d for this timing to be when vccglanpll drops to 1.425 v or less, as measured at the ich10. this timing applies on ly to platforms using ich10 integrated gbe lan. 8. maximum timing may be exceeded in a intel management engine enabled system. 9. vccsus supplies include vccsus3_3, v5ref_ sus, vccsushda, vccl an3_3 (if lan powered in s3/s4/s5), and vcccl3_3 (if controller link powered in s3/s4/s5). 10. vcc includes vcc1_5_a, vcc1_5_b, vcc3_3, vcc1_1, vccusbpll, vc cdmipll, vccsatapll, v5ref, v_cpu_io, vccdmi, vcchda, vccg lanpll, vccglan3_3 and vccglan1_5 (if integrated gigabit lan enabled), vcclan3_3 (i f lan only power in s0), and vcccl3_3 (if controller link only powered in s0). t214 vcc supplies active to pwrok note: pwrok assertion indicates that pciclk has been stable for at least 1ms. 99 ? ms 10 8-14 8-15 8-17 t217 pwrok and vrmpwr gd active to sus_stat# inactive and processor interface signals latched to strap value (consumer only) 33 71 rtcclk 5, 6, 8 8-15 8-17 t217 pwrok and vrmpwr gd active to sus_stat# inactive and processor interface signals latched to strap value (corporate only) 33 ? rtcclk 5, 6, 8 8-15 8-17 t218 sus_stat# inactive to pltrst# inactive (consumer only) 2 ? rtcclk 6 8-15 8-17 t218 sus_stat# inactive to pltrst# inactive (corporate only) 60 ? s 8-15 8-17 t219 pltrst# assertion to vccglanpll inactive for platforms using ich10 integrated gbe lan 200 ? s7 t228 hda_rst# active low pulse width 1 ? s t229 hda_rst# inactive to hda_bit_clk startup delay 162.8 ? ns table 8-21. power sequencing and reset signal timings (sheet 2 of 2) sym parameter min max units notes fig http://www..net/ datasheet pdf - http://www..net/ datasheet 277 electrical characteristics . table 8-22. power management timings (sheet 1 of 3) sym parameter min max units notes fig t230 vccsus active to slp_s5#, slp_s4#, slp_s3#, sus_stat#, pltrst# and pcirst#active ?50 ns 8-15 t231 t232 rsmrst# inactive to susclk running, slp_s5# inactive ? 110 ms 6, 22 8-15 t233 slp_s5# inactive to slp_s4# inactive see note below 8 8-15 t234 slp_s4# inactive to slp_s3# inactive 1 note 16 rtcclk 1 8-15 8-17 8-21 8-22 t250 processor i/f signals latched prior to stpclk# active 0? 9 8-18 8-19 8-20 t251 bus master idle to dpslp# active 3.36 ? s 11 8-19 8-20 t252 dmi message to pmsync# assertion 0 ? pciclk t253 dpslp# active to stp_cpu# active 1 1 pciclk 3 8-19 8-20 t254 stp_cpu# active to processor clock stopped 0 ? pciclk 3, 10 8-19 8-20 t255 stp_cpu# active to dprstp#, dprslpvr active 0? 8-20 t265 break event to dprstp#, dprslpvr inactive (c4 exit) 1.5 1.8 s 12 8-20 t266a dprslpvr, dprstp# inactive to stp_cpu# inactive and cpu vcc ramped programable. see d31:f0:aa, bits 3:2 s 8-20 t267 break event to stp_cpu# inactive (c3 exit) 6note 14pciclk 3, 13, 14 8-19 t268 stp_cpu# inactive to processor clock running 0 3 pciclk 3, 10 8-19 8-20 t269 stp_cpu# inactive to dpslp# inactive 1 1 pciclk 3, 7 8-19 8-20 t270 dpslp# inactive to stpclk# inactive 0 s 8-19 8-20 t273 break event to stpclk# inactive (c2 exit) 0ns 8-18 t274 stpclk# inactive to processor i/f signals unlatched 89pciclk3, 9 8-18 8-19 8-20 t280 stpclk# active to dmi message 0 pciclk 2 8-16 8-17 t281 dmi message to cpuslp# active 60 63 pciclk 3 8-16 http://www..net/ datasheet pdf - http://www..net/ electrical characteristics 278 datasheet t283 dmi message to sus_stat# active 2 rtcclk 1 8-17 t284 sus_stat# active to pltrst#, pcirst# active 7 17 rtcclk 1 8-17 t287 pltrst#, pcirst# active to slp_s3# active (consumer only) 1 2 rtcclk 1 8-17 t287 pltrst#, pcirst# active to slp_s3# active (corporate only) 1 ? rtcclk 1 8-17 t289 slp_s3# active to pwrok, vrmpwrgd inactive 0ms4 8-17 t291 slp_s3# active to slp_s4# active (consumer only) 1 2 rtcclk 1 8-17 t291 slp_s3# active to slp_s4# active (corporate only) 1 ? rtcclk 1 8-17 t294 pwrok, vrmpwrgd inactive to vcc supplies inactive (nominal voltage -5%) 20 ns 23, 25 8-17 8-25 t295 slp_s4# active to slp_s5# active (consumer only) 1 2 rtcclk 1, 5 8-17 t295 slp_s4# active to slp_s5# active (corporate only) 1 ? rtcclk 1, 5 8-17 t296 wake event to slp_s5# inactive 1 10 rtcclk 1 8-17 t297 slp_s5# inactive to slp_s4# inactive 1 ? rtcclk 8 8-17 8-21 8-22 8-23 t298 s4_state# inactive to slp_s3# inactive (consumer only) 1 note 16 rtcclk 1 8-23 t298 s4_state# inactive to slp_s3# inactive (corporate only) 1 ? rtcclk 1 8-23 t299 s4 wake event to slp_s4# inactive (s4 wake) see note below 8 8-17 t300 s3 wake event to slp_s3# inactive (s3 wake) (consumer only) 0 small as possible rtcclk 1 8-17 t300 s3 wake event to slp_s3# inactive (s3 wake) (corporate only) 0 ? rtcclk 1 8-17 t301 s1 wake event to stpclk# inactive 9 pciclk 8-16 t302 slp_m# inactive to slp_s3# inactive 10 ns 8-21 t304 rsmrst# deassertion to lan_rst# deassertion 0ms17 table 8-22. power management timings (sheet 2 of 3) sym parameter min max units notes fig http://www..net/ datasheet pdf - http://www..net/ datasheet 279 electrical characteristics notes: 1. these transitions are clocked off the intern al rtc. 1 rtc clock is approximately from 28.992 s to 32.044 s. 2. the ich10 stpclk# assertion will trigger the processor to send a stop grant acknowledge cycle. the timing for this cycle getting to th e ich10 is dependant on the processor and the memory controller. 3. these transitions are clocked off the 33 mh z pciclk. 1 pciclk is approximately 30 ns. 4. the ich10 has no maximum timing requirement fo r this transition. it is up to the system designer to determine if the slp_s3#, slp_ s4# and slp_s5# signals are used to control the power planes. 5. if the transition to s5 is due to power button override, slp_s3#, slp_s4# and slp_s5# are asserted together similar to timing t287 (pcirst# active to slp_s3# active). 6. if there is no rtc battery in the system, so vccrtc and the vccsus supplies come up together, the delay from rtcrst# and rsmrst# inactive to susclk toggling may be as much as 2.5 s. 7. this value is programmable in multiples of 1024 pci clks. maximum is 8192 pci clks (245.6 s). 8. the min/max times depend on the progra mming of the ?slp_s4# minimum assertion width? and the ?slp_s4# as sertion stretch enable bits (d31:f0:a4h bits 5:3)?. 9. note that this does not apply for synchronous smis. 10. this is a clock generator specification 11. if the (g)mch does not have the cpuslp# signal, then the minimum value can be 16 pciclk. 12. this is non-zero to enforce the minimum assert time for dprslpvr. if the minimum assert time for dprslpvr has been met, then this is pe rmitted to be 0. 13. this is non-zero to enforce the minimum assert time for stp_cpu#. if the minimum assert time for stp_cpu# has been met, then this is permitted to be 0. 14. this value should be at most a few clocks greater than the minimum. 15. when intel amt enabled, s4_state# indicates if system is in s4 state or below. 16. for t234 and t298, the slp_m# stretching lo gic can push the max value much larger than the min (e.g., up to 3 seconds). with the installation of the intel manageability engine t305a lan power rails active to lan_rst# deassertion 1ms18 t305b lan_rst# assertion to lan power rails inactive 20 ns 25 t306 lanrst# assertion to pwrok assertion 0 ms t307 slp_s3# active to vcc supplies inactive (nominal voltage -5%) 5us24 8-17 t308a rsmrst# deassertion to clpwrok assertion 0ms t308b controller link power rails active to clpwrok assertion 1ms t308c clpwrok assertion to pwrok assertion 0 ms other timings t310 thrmtrip# active to slp_s3#, slp_s4#, slp_s5# active 175 ns t311 rsmrst# rising edge transition from 20% to 80% 50 s t312 rsmrst# falling edge transition 21 t313 slp_m# active to rsmrst# active 500 s table 8-22. power management timings (sheet 3 of 3) sym parameter min max units notes fig http://www..net/ datasheet pdf - http://www..net/ electrical characteristics 280 datasheet firmware, the max value of t234 and t298 is 99 ms. without the installation of the firmware, the max value is 4 rtc clocks. 17. rsmrst# must de-assert at or before lan_rst# de-assertion. 18. measured from vcclan3_3 or vcclan1_1 power wi thin voltage specification (which ever is later in time) to lan_rst# = (vih+vil)/2. it is acceptable to use an rc circuit sourced from vcclan3_3 to create lan_rst#. the rising edge of lan_rst# needs to be a clean, monotonic edge for frequency content below 10 mhz. 19. if integrated lan is supported, lan_rst# must be de-asserted at or before pwrok assertion. 20. if integrated lan is not supported, lan_rst# should be tied to ground and must never de-assert. 21. rsmrst# falling edge must transition to 0.8 v or less before vccsus3_3 drops to 2.1 v 22. if bit 0 of section 13.8.1.3 is set to a 1, slp_s5# will not be de-asserted until a wake event is detected. if bit 0 is set to 0, slp_s5# will de-assert within the specification listed in the table. 23. t294 is not applied to v5ref. v5ref timi ngs are bounded by power sequencing. t294 applies during s0 to s3/s4/s5 and s0 to g3 transitions. 24. t307 is applicable in s0 to sx transitions. 25. a power rail is considered to be inactive when the rail is at its nominal voltage minus 5% or less. 8.5 timing diagrams figure 8-1. clock timing figure 8-2. valid delay from rising clock edge 2.0v 0.8v period high time low time fall time rise time clock 1.5v valid delay vt output http://www..net/ datasheet pdf - http://www..net/ datasheet 281 electrical characteristics figure 8-3. setup and hold times figure 8-4. float delay figure 8-5. pulse width figure 8-6. output enable delay clock vt input hold time setup time vt 1.5v input vt output float delay vt pulse width vt clock output output enable delay vt 1.5v http://www..net/ datasheet pdf - http://www..net/ electrical characteristics 282 datasheet figure 8-7. usb rise and fall times figure 8-8. usb jitter figure 8-9. usb eop width differential data lines 90% 10% 10% 90% t r t f rise time fall time c l c l low-speed: 75 ns at c l = 50 pf, 300 ns at c l = 350 pf full-speed: 4 to 20 ns at c l = 50 pf high-speed: 0.8 to 1.2 ns at c l = 10 pf paired transitions consecutive transitions crossover points t period differential data lines jitter differential data lines eop width data crossover level tperiod http://www..net/ datasheet pdf - http://www..net/ datasheet 283 electrical characteristics figure 8-10. smbus transaction figure 8-11. smbus timeout t130 smbclk smbdata t131 t19 t134 t20 t21 t135 t132 t18 t13 3 start stop t137 clk ack clk ack t138 t138 smbclk smbdata http://www..net/ datasheet pdf - http://www..net/ electrical characteristics 284 datasheet figure 8-12. spi timings figure 8-13. intel ? high definition audio input and output timings t182 t182 spi_clk spi_mosi spi_miso t184 t183 t185 spi_cs[1:0]# t186 t187 hda_sdout hda_sdin[3:0] hda_bit_clk t143 t143 t144 t144 t145 t146 http://www..net/ datasheet pdf - http://www..net/ datasheet 285 electrical characteristics notes: 1. other power includes vccusbpll, vccdmipll, and vccsat apll. all of these power signals must independently meet the timings shown in the figure. there are no timing interdependencies between vcc1 _1 and these other power signals. there are also no timing interdependencies for these power si gnals, including vcc1_1, to vcc3_3 and vcc1_5_a/vcc1_5_b. 2. pwrok must not glitch, even if rsmrst# is low. 3. vcclan includes vcclan3_ 3, vcclan1_1, and vcccl3_3. 4. other power figure 8-14. power sequencing and reset signal timings vccrtc v_cpu_io vccsus3_3 rtcrst# rsmrst# t200 t201 v5ref_sus v5ref pwrok vcc3_3 vccsus1_1 t203 t204 t209 t211 t214 t202 t213 vcc1_5_a, vcc1_5_b vcc1_1 and other power 1 lan_rst# vcclan 3 t305a http://www..net/ datasheet pdf - http://www..net/ electrical characteristics 286 datasheet note: 1. vcc includes vcc1_5_a, vcc1_5_b, vcc3_3, vcc1_1, vccusbpll, vc cdmipll, vccsatapll, v5ref, v_cpu_io, vccdmi, vcchda, vccg lanpll, vccglan3_3 and vccglan1_5 (if integrated gigabit lan enabled), vcclan3_3 (i f lan only power in s0), and vcccl3_3 (if controller link only powered in s0). 2. vcclan includes vcclan3_3, vcclan1_1, and vcccl3_3. 3. vccsus includes vccsus3_3, v5ref_sus, vc csushda, vcclan3_3 (i f lan powered in s3/ s4/s5), and vcccl3_3 (if controll er link powered in s3/s4/s5). figure 8-15. g3 (mechanical off) to s0 timings vccsus 3 running susclk slp_s3# vcc 1 pwrok sus_stat# pltrst# processor i/f signals stpclk# dmi message rsmrst# t204 t214 t212 t218 t230 t231 g3 s3 s0 s0 state g3 s5 system state s4 slp_s4# slp_s5# t232 t233 t234 strap values normal operation vrmpwrgd t217 vcclan 2 lan_rst# t305a http://www..net/ datasheet pdf - http://www..net/ datasheet 287 electrical characteristics note: vcc includes vcc1_5_a, vcc1_5_b, vcc3_3, vcc1_1, vccusbpll, vccdmipll, and vccsatapll. figure 8-16. s0 to s1 to s0 timings t280 s0 s0 s1 s1 s1 s0 s0 state stpclk# dmi message wake event t301 figure 8-17. s0 to s5 to s0 timings stp_cpu#, cpuslp#, dpslp#, dprstp# pltrst# pcirst# slp_s3# slp_s5# wake event pwrok vcc 1 s0 s0 s3 s3 s5 s3/s4/s5 s0 s0 t295 t289 t296 t214 t217 t218 stp_pci# stpclk# dmi message dprslpvr t280 t283 t285 t287 t286 sus_stat# s4 slp_s4# t291 t297 t300 t234 t299 t302 slp_m# vrmpwrgd t307 t212 http://www..net/ datasheet pdf - http://www..net/ electrical characteristics 288 datasheet figure 8-18. c0 to c2 to c0 timings figure 8-19. c0 to c3 to c0 timings unlatched latched unlatched cpu i/f signals stpclk# break event t250 t273 t274 unlatched latched cpu i/f signals stpclk# break event bus master stp_cpu# t250 t251 t253 t268 t269 t274 active idle dpslp# t270 unlatched cpu clocks running running stopped t267 t254 http://www..net/ datasheet pdf - http://www..net/ datasheet 289 electrical characteristics figure 8-20. c0 to c4 to c0 timings unlatched cpu i/f signals stpclk# break event bus master stp_cpu# t250 t251 t253 t266a t269 t274 t270 dprstp# dpslp# active idle dprslpvr unlatched cpu clocks running running t254 t255 cpu vcc t265 stopped t268 latched http://www..net/ datasheet pdf - http://www..net/ electrical characteristics 290 datasheet notes: 1. t290 is also applicable when the system transitions from s0 to g3. note: when both the host and intel management en gine boot after g3, slp_m# does not have any timing dependency on other sleep control signals. slp_m# will be de-asserted some time between slp_s5# de-asserti on and slp_s3# de-assertion. figure 8-21. sleep control sign al relationship - host boots and intel management engine off slp_m# slp_s5# slp_s4# slp_s3# t297 t234 s4_state# t302 figure 8-22. sleep control sign al relationship - host and in tel management engine boot after g3 slp_m# slp_s5# slp_s4# slp_s3# t234 s4_state# t297 http://www..net/ datasheet pdf - http://www..net/ datasheet 291 electrical characteristics note: vcc includes vcc1_5_a, vcc1_5_b, vcc3_3, vcc1_1, vccusbpll, vccdmipll, and vccsatapll. figure 8-23. sleep control sign al relationship - host stays in s5 and intel management engine boots after g3 figure 8-24. s4, s5/m1 to s0/m0 slp_m# slp_s5# slp_s4# slp_s3# wake event s4_state# t298 t297 t303 slp_m# slp_s5# slp_s4# slp_s3# w ake event s4_state# t298 t297 t303 figure 8-25. s0 to s3/s4/s5 and g3 timings pwrok vcc t294 http://www..net/ datasheet pdf - http://www..net/ electrical characteristics 292 datasheet http://www..net/ datasheet pdf - http://www..net/ datasheet 293 register and memory mapping 9 register and memory mapping the ich10 contains registers that are located in the processor?s i/o space and memory space and sets of pci configuration registers that are located in pci configuration space. this chapter describes the ich10 i/ o and memory maps at the register-set level. register access is also described. register-level address maps and individual register bit descriptions are provided in th e following chapters. the following notations and definitions are used in the regist er/instruction description chapters. ro read only. in some cases, if a register is read only, writes to this register location have no effect. however, in other cases, two separate registers are located at the same location where a read accesses one of the registers and a write accesses the other register. see the i/o and memory map tables for details. wo write only. in some cases, if a register is write only, reads to this register location have no effect. however, in other cases, two separate registers are located at the same location where a read accesses one of the registers and a write accesses the other register. see the i/o and memory map tables for details. r/w read/write. a register with this attribute can be read and written. r/wc read/write clear. a register bit with this attribute can be read and written. however, a write of 1 clears (sets to 0) the corresponding bit and a write of 0 has no effect. r/wo read/write-once. a register bit with this attribute can be written only once after power up. after the first write, the bit becomes read only. r/wlo read/write, lock-once. a register bit with this attribute can be written to the non-locked value multiple times, but to the locked value only once. after the locked value has been written, the bit becomes read only. reserved the value of reserved bits must never be changed. for details see section 9.2 . default when ich10 is reset, it sets its registers to predetermined default states. the default st ate represents the minimum functionality feature set required to successfully bring up the system. hence, it does not represent the optimal system configuration. it is the responsi bility of the system initialization software to determine configuration, operating parameters, and optional system features that are applicable, and to program the ich10 registers accordingly. bold register bits that are highlighted in bold text indicate that the bit is implemented in the ich10. register bits that are not implemented or are hardwired will remain in plain text. http://www..net/ datasheet pdf - http://www..net/ register and memory mapping 294 datasheet 9.1 pci devices and functions the intel ich10 incorporates a variety of pci devices and functions, as shown in ta b l e 9 - 1 . there are seven logical devices for consumer components, and 8 logical devices for corporate components. the first is the dmi-to-pci bridge (device 30). the second device (device 31) contains most of the standard pci functions that always existed in the pci-to-isa bridges (south br idges), such as the intel piix4. the third and fourth (device 29 and device 26) are the usb and usb2 host controller devices. the fifth (device 28) is pci express device. the sixth (device 27) is hd audio controller device. the seventh (device 25) is the gigabit ethernet controller device. if for some reason, the particular system platform does not want to support any one of the device functions, with the exception of d30:f0, they can individually be disabled. the integrated gigabit ethernet controller w ill be disabled if no platform lan connect component is detected (see chapter 5.3 ). when a function is disabled, it does not appear at all to the software. a disabled function will not respond to any register reads or writes, insuring that these devices appear hidden to software. b notes: 1. the pci-to-lpc bridge contai ns registers that control lp c, power manage ment, system management, gpio, proces sor interface, rtc, inte rrupts, timers, and dma. table 9-1. pci devi ces and functions bus:device:function function description bus 0:device 30:function 0 pci-to-pci bridge bus 0:device 31:function 0 lpc controller 1 bus 0:device 31:function 2 sata controller #1 bus 0:device 31:function 3 smbus controller bus 0:device 31:function 5 sata controller #2 3 bus 0:device 31:function 6 thermal subsystem bus 0:device 29:function 0 usb uhci controller #1 bus 0:device 29:function 1 usb uhci controller #2 bus 0:device 29:function 2 usb uhci controller #3 bus 0:device 29:function 3 usb uhci controller #6 2 bus 0:device 29:function 7 usb ehci controller #1 bus 0:device 26:function 0 usb uchi controller #4 bus 0:device 26:function 1 usb uhci controller #5 bus 0:device 26:function 2 usb uhci controller #6 2 bus 0:device 26:fucntion 7 usb ehci controller #2 bus 0:device 28:function 0 pci express* port 1 bus 0:device 28:function 1 pci express port 2 bus 0:device 28:function 2 pci express port 3 bus 0:device 28:function 3 pci express port 4 bus 0:device 28:function 4 pci express port 5 bus 0:device 28:function 5 pci express port 6 bus 0:device 27:function 0 intel ? high definition audio controller bus 0:device 25:function 0 gigabit ethernet controller http://www..net/ datasheet pdf - http://www..net/ datasheet 295 register and memory mapping 2. the ich10 can optionally configure the usb ports from a 6-6 configuration into a 8-4 configuration, with 8 ports on d29:f7 ehci and 4 ports on d26:f7 ehci. in the 8-4 configuration uhci #6 will be mapped to d29:f3. in the 6-6 configuration uhci #6 will be mapped to d26:f2. 3. sata controller 2 (d31:f5) is only visible in ich10 desktop components and when d31:f2 cc.scc=01h. 9.2 pci configuration map each pci function on the ich10 has a set of pci configuration registers. the register address map tables for these register sets are included at the beginning of the chapter for the particular function. configuration space registers are accessed th rough configuration cycles on the pci bus by the host bridge using configur ation mechanism #1 detailed in the pci local bus specification, revision 2.3 . some of the pci registers contain reserved bits. software must deal correctly with fields that are reserved. on reads, software must use appropriate masks to extract the defined bits and not rely on reserved bits being any particular value. on writes, software must ensure that the values of re served bit positions are preserved. that is, the values of reserved bit positions must fi rst be read, merged with the new values for other bit positions and then written back. no te the software does not need to perform read, merge, write operation for the configuration address register. in addition to reserved bits within a register, the configuration space contains reserved locations. software should not write to re served pci configuration locations in the device-specific region (above address offset 3fh). 9.3 i/o map the i/o map is divided into fixed and variable address ranges. fixed ranges cannot be moved, but in some cases can be disabled. variable ranges can be moved and can also be disabled. 9.3.1 fixed i/o address ranges ta b l e 9 - 2 shows the fixed i/o decode ranges from the processor perspective. note that for each i/o range, there may be separate behavior for reads and writes. dmi (direct media interface) cycles that go to target ranges that are marked as ?reserved? will not be decoded by the ich10, and will be pa ssed to pci unless the subtractive decode policy bit is set (d31:f0:offset 42h, bit 0). if a pci master targets one of the fixed i/o target ranges, it will be positively decoded by the ich10 in medium speed. address ranges that are not listed or marked ?reserved? are not decoded by the ich10 (unless assigned to one of the variable ranges). http://www..net/ datasheet pdf - http://www..net/ register and memory mapping 296 datasheet table 9-2. fixed i/o ranges decoded by intel ? ich10 (sheet 1 of 2) i/o address read target write target internal unit 00h?08h dma controller dma controller dma 09h?0eh reserved dma controller dma 0fh dma controller dma controller dma 10h?18h dma controller dma controller dma 19h?1eh reserved dma controller dma 1fh dma controller dma controller dma 20h?21h interrupt controller in terrupt controller interrupt 24h?25h interrupt controller in terrupt controller interrupt 28h?29h interrupt controller in terrupt controller interrupt 2ch?2dh interrupt controller interrupt controller interrupt 2e?2f lpc sio lpc sio forwarded to lpc 30h?31h interrupt controller in terrupt controller interrupt 34h?35h interrupt controller in terrupt controller interrupt 38h?39h interrupt controller in terrupt controller interrupt 3ch?3dh interrupt controller interrupt controller interrupt 40h?42h timer/counter timer/counter pit (8254) 43h reserved timer/counter pit 4e?4f lpc sio lpc sio forwarded to lpc 50h?52h timer/counter timer/counter pit 53h reserved timer/counter pit 60h microcontroller microcon troller forwarded to lpc 61h nmi controller nmi controller processor i/f 62h microcontroller microcon troller forwarded to lpc 64h microcontroller microcon troller forwarded to lpc 66h microcontroller microcon troller forwarded to lpc 70h reserved nmi and rtc controller rtc 71h rtc controller rtc controller rtc 72h rtc controller nmi and rtc controller rtc 73h rtc controller rtc controller rtc 74h rtc controller nmi and rtc controller rtc 75h rtc controller rtc controller rtc 76h rtc controller nmi and rtc controller rtc 77h rtc controller rtc controller rtc 80h dma controller, or lpc, or pci dma controller and lpc or pci dma 81h?83h dma controller dma controller dma http://www..net/ datasheet pdf - http://www..net/ datasheet 297 register and memory mapping note: 1. a read to this address will subtractivel y go to pci, where it will master abort. 84h?86h dma controller dma controller and lpc or pci dma 87h dma controller dma controller dma 88h dma controller dma controller and lpc or pci dma 89h?8bh dma controller dma controller dma 8ch?8eh dma controller dma controller and lpc or pci dma 08fh dma controller dma controller dma 90h?91h dma controller dma controller dma 92h reset generator reset generator processor i/f 93h?9fh dma controller dma controller dma a0h?a1h interrupt controller interrupt controller interrupt a4h?a5h interrupt controller interrupt controller interrupt a8h?a9h interrupt controller interrupt controller interrupt ach?adh interrupt controller interrupt controller interrupt b0h?b1h interrupt controller interrupt controller interrupt b2h?b3h power management power management power management b4h?b5h interrupt controller interrupt controller interrupt b8h?b9h interrupt controller interrupt controller interrupt bch?bdh interrupt controller interrupt controller interrupt c0h?d1h dma controller dma controller dma d2h?ddh reserved dma controller dma deh?dfh dma controller dma controller dma f0h pci and master abort 1 ferr#/ignne# / interrupt controller processor i/f 170h?177h sata controller or pci sata controller or pci forwarded to sata 1f0h?1f7h sata controller or pci sata controller or pci forwarded to sata 376h sata controller or pci sata controller or pci forwarded to sata 3f6h sata controller or pci sata controller or pci forwarded to sata 4d0h?4d1h interrupt controller interrupt controller interrupt cf9h reset generator reset generator processor i/f table 9-2. fixed i/o ranges decoded by intel ? ich10 (sheet 2 of 2) i/o address read target write target internal unit http://www..net/ datasheet pdf - http://www..net/ register and memory mapping 298 datasheet 9.3.2 variable i/o decode ranges ta b l e 9 - 3 shows the variable i/o decode ranges. they are set using base address registers (bars) or other configuration bits in the various pci configuration spaces. the pnp software (pci or acpi) can use their configuration mechanisms to set and adjust these values. warning: the variable i/o ranges should not be set to conflict with the fixed i/o ranges. unpredictable results if the configuration soft ware allows conflicts to occur. the ich10 does not perform any checks for conflicts. note: 1. decode range size determined by d31:f0:adh:bits 5:4 table 9-3. variable i/o decode ranges range name mappable size (bytes) target acpi anywhere in 64 kb i/o space 64 power management ide bus master anywhere in 64 kb i/o space 16 ide unit native ide command anywhere in 64 kb i/o space 8 ide unit native ide control anywhere in 64 kb i/o space 4 ide unit usb uhci controller #1 anywhere in 64 kb i/o space 32 usb unit 1 usb uhci controller #2 anywhere in 64 kb i/o space 32 usb unit 2 usb uhci controller #3 anywhere in 64 kb i/o space 32 usb unit 3 usb uhci controller #4 anywhere in 64 kb i/o space 32 usb unit 4 usb uhci controller #5 anywhere in 64 kb i/o space 32 usb unit 5 usb uhci controller #6 anywhere in 64 kb i/o space 32 usb unit 6 smbus anywhere in 64 kb i/o space 32 smb unit tco 96 bytes above acpi base 32 tco unit gpio anywhere in 64 kb i/o space 64 gpio unit parallel port 3 ranges in 64 kb i/o space 8 lpc peripheral serial port 1 8 ranges in 64 kb i/o space 8 lpc peripheral serial port 2 8 ranges in 64 kb i/o space 8 lpc peripheral floppy disk controller 2 ranges in 64 kb i/o space 8 lpc peripheral lan anywhere in 64 kb i/o space 32 lan unit lpc generic 1 anywhere in 64 kb i/o space 4 to 256 lpc peripheral lpc generic 2 anywhere in 64 kb i/o space 4 to 256 lpc peripheral lpc generic 3 anywhere in 64 kb i/o space 4 to 256 lpc peripheral lpc generic 4 anywhere in 64 kb i/o space 4 to 256 lpc peripheral i/o trapping ranges anywhere in 64 kb i/o space 1 to 256 trap on backbone http://www..net/ datasheet pdf - http://www..net/ datasheet 299 register and memory mapping 9.4 memory map ta b l e 9 - 4 shows (from the processor perspective) the memory ranges that the ich10 decodes. cycles that arrive from dmi that are not directed to any of the internal memory targets that decode directly from dmi will be driven out on pci unless the subtractive decode policy bit is set (d31:f0:offset 42h, bit 0). pci cycles generated by external pci masters will be positively decoded unless they fall in the pci-to-pci bridge memory forwarding ranges (those addresses are reserved for pci peer-to-peer traffic). if the cycle is not in the internal lan controller?s range, it will be forwarded up to dmi. software must not attempt locks to the ich10?s memory- mapped i/o ranges for ehci and hpet. if attempted, the lock is not honored which means potential deadlock conditions may occur. table 9-4. memory decode ranges from processor perspective (sheet 1 of 2) memory range target dependency/comments 0000 0000h?000d ffffh 0010 0000h?tom (top of memory) main memory tom registers in host controller 000e 0000h?000e ffffh firmware hub bit 6 in firmware hub decode enable register is set 000f 0000h?000f ffffh firmware hub bit 7 in firmware hub decode enable register is set fec_ _000h?fec_ _040h (corporate only) io(x) apic inside ich10 _ _is controlled via apic range select (asel) field and apic enable (aen) bit fec0 _000h?fec0 _040h (consumer only) io(x) apic inside ich10 _ is controlled via apic range select (asel) field and apic enable (aen) bit fec1 0000h?fec1 7fff pci express* port 1 pci express* root port 1 i/oxapic enable (pae) set fec1 8000h?fec1 8fffh pci express* port 2 pci express* root port 2 i/oxapic enable (pae) set fec2 0000h?fec2 7fffh pci express* port 3 pci express* root port 3 i/oxapic enable (pae) set fec2 8000h?fec2 8fffh pci express* port 4 pci express* root port 4 i/oxapic enable (pae) set fec3 0000h?fec3 7fffh pci express* port 5 pci express* root port 5 i/oxapic enable (pae) set fec3 8000h?fec3 8fffh pci express* port 6 pci express* root port 6 i/oxapic enable (pae) set fed4 0000h?fed4 bfffh tpm on lpc ffc0 0000h?ffc7 ffffh ff80 0000h?ff87 ffffh firmware hub (or pci) 2 bit 8 in firmware hub decode enable register is set ffc8 0000h?ffcf ffffh ff88 0000h?ff8f ffffh firmware hub (or pci) 2 bit 9 in firmware hub decode enable register is set ffd0 0000h?ffd7 ffffh ff90 0000h?ff97 ffffh firmware hub (or pci) 2 bit 10 in firmware hub decode enable register is set ffd8 0000h?ffdf ffffh ff98 0000h?ff9f ffffh firmware hub (or pci) 2 bit 11 in firmware hub decode enable register is set http://www..net/ datasheet pdf - http://www..net/ register and memory mapping 300 datasheet notes: 1. software must not at tempt locks to memory mapped i/o ranges for usb ehci or high precision event timers. if attempted, the lo ck is not honored, which means potential deadlock conditions may occur. 2. pci is the target when the boot bios destination selection bits are set to 10b (chipset config registers:offset 3401 bits 11:10). when pci selected, the firmware hub decode enable bits have no effect. 9.4.1 boot-block update scheme the ich10 supports a ?top-block swap? mode that has the ich10 swap the top block in the firmware hub (the boot block) with anothe r location. this allows for safe update of the boot block (even if a power failure occurs). when the ?top_swap? enable bit is set, the ich10 will invert a16 for cycles targ eting firmware hub space. when this bit is 0, the ich10 will not invert a16. this bit is automatically set to 0 by rtcrst#, but not by pltrst#. ffe0 000h?ffe7 ffffh ffa0 0000h?ffa7 ffffh firmware hub (or pci) 2 bit 12 in firmware hub decode enable register is set ffe8 0000h?ffef ffffh ffa8 0000h?ffaf ffffh firmware hub (or pci) 3 bit 13 in firmware hub decode enable register is set fff0 0000h?fff7 ffffh ffb0 0000h?ffb7 ffffh firmware hub (or pci) 2 bit 14 in firmware hub decode enable register is set fff8 0000h?ffff ffffh ffb8 0000h?ffbf ffffh firmware hub (or pci) 2 always enabled. the top two, 64 kb blocks of this range can be swapped, as described in section 7.4.1 . ff70 0000h?ff7f ffffh ff30 0000h?ff3f ffffh firmware hub (or pci) 2 bit 3 in firmware hub decode enable register is set ff60 0000h?ff6f ffffh ff20 0000h?ff2f ffffh firmware hub (or pci) 2 bit 2 in firmware hub decode enable register is set ff50 0000h?ff5f ffffh ff10 0000h?ff1f ffffh firmware hub (or pci) 2 bit 1 in firmware hub decode enable register is set ff40 0000h?ff4f ffffh ff00 0000h?ff0f ffffh firmware hub (or pci) 2 bit 0 in firmware hub decode enable register is set 128 kb anywhere in 4-gb range integrated lan controller enable via bar in de vice 25:function 0 (integrated lan controller) 1 kb anywhere in 4-gb range usb ehci controller #1 1 enable via standard pci mechanism (device 29, function 7) 1 kb anywhere in 4-gb range usb ehci controller #2 1 enable via standard pci mechanism (device 26, function 7) 512 b anywhere in 64-bit addressing space intel ? high definition audio host controller enable via standard pci mechanism (device 27, function 0) fed0 x000h?fed0 x3ffh high precision event timers 1 bios determines the ?fixed? location which is one of four, 1-kb ranges where x (in the first column) is 0h, 1h, 2h, or 3h. all other pci none table 9-4. memory decode ranges from processor perspect ive (sheet 2 of 2) memory range target d ependency/comments http://www..net/ datasheet pdf - http://www..net/ datasheet 301 register and memory mapping the scheme is based on the concept that the top block is reserved as the ?boot? block, and the block immediately below the top block is reserved for doing boot-block updates. the algorithm is: 1. software copies the top block to the block immediately below the top 2. software checks that the copied block is correct. this could be done by performing a checksum calculation. 3. software sets the top_swap bit. this will invert a16 for cycles going to the firmware hub. processor access to ffff_0000h through ffff_ffffh will be directed to fffe_0000h through fffe_ffffh in the firmware hub, and processor accesses to fffe_0000h through fffe_ffff will be directed to ffff_0000h through ffff_ffffh. 4. software erases the top block 5. software writes the new top block 6. software checks the new top block 7. software clears the top_swap bit 8. software sets the top_swap lock-down bit if a power failure occurs at any point after st ep 3, the system will be able to boot from the copy of the boot block that is stored in the block below the top. this is because the top_swap bit is backed in the rtc well. note: the top-block swap mode may be forced by an external strapping option (see section 2.25.1 ). when top-block swap mode is forced in this manner, the top_swap bit cannot be cleared by software. a re-boot with the strap removed will be required to exit a forced top-block swap mode. note: top-block swap mode only affects accesses to the firmware hub space, not feature space. note: the top-block swap mode has no effect on accesses below fffe_0000h. http://www..net/ datasheet pdf - http://www..net/ register and memory mapping 302 datasheet http://www..net/ datasheet pdf - http://www..net/ datasheet 303 chipset configuration registers 10 chipset configuration registers this section describes all registers and base functionality that is related to chipset configuration and not a specific interface (s uch as lpc, pci, or pci express*). it contains the root complex register block, which describes the behavior of the upstream internal link. this block is mapped into memory space, using the root complex base address (rcba) register of the pci-to-lpc bridge. accesses in this space must be limited to 32-(dw) bit quantities. burst accesses are not allowed. all chipset configuration registers are located in the core well unless otherwise indicated. 10.1 chipset configuration registers (memory space) note: address locations that are not shown should be treated as reserved (see section 9.2 for details). . table 10-1. chipset configurat ion register memory map (mem ory space) (sheet 1 of 4) offset mnemonic register name default type 0000?0003h vch virtual channe l capability header 10010002h r/wo 0004?0007h vcap1 virtual channel capability #1 00000801h ro, r/wo 0008?000bh vcap2 virtual channel capability #2 00000001h ro 000c?000dh pvc port vc control 0000h ro, r/w 000e?000fh pvs port vc status 0000h ro 0010?0013h v0cap vc 0 resource capability 00000001h ro 0014?0017h v0ctl vc 0 resource control 800000ffh r/w, ro 001a?001bh v0sts vc 0 resource status 0000h ro 001c?001fh v1cap vc 1 resource capability 03008011h r/wo, ro 0020?0023h v1ctl vc 1 resource control 00000000h r/w 0026?0027h v1sts vc 1 resource status 0000h ro 0030-006fh (corporate only) ?reserved ? ? 0030-006fh (consumer only) pat port arbitration table 0088-008bh cir1 chipset initialization register 1 00000000h r/wo 00ac-00afh rec root error command 0000h r/w 0100?0103h rctcl root complex topology capability list 1a010005h ro 0104?0107h esd element self description 00000802h r/wo, ro 0110?0113h uld upstream link descriptor 00000001h r/wo, ro http://www..net/ datasheet pdf - http://www..net/ chipset configuration registers 304 datasheet 0118?011fh ulba upstream link base address 0000000000000000h r/wo 0120?0123h rp1d root port 1 descriptor 01xx0002h r/wo, ro 0128?012fh rp1ba root port 1 base address 00000000000e0000h ro 0130?0133h rp2d root port 2 descriptor 02xx0002h r/wo, ro 0138?013fh rp2ba root port 2 base address 00000000000e1000h ro 0140?0143h rp3d root port 3 descriptor 03xx0002h r/wo, ro 0148?014fh rp3ba root port 3 base address 00000000000e2000h ro 0150?0153h rp4d root port 4 descriptor 04xx0002h r/wo, ro 0158?015fh rp4ba root port 4 base address 00000000000e3000h ro 0160?0163h hdd intel ? high definition audio descriptor 15xx0002h r/wo, ro 0168?016fh hdba intel high definition audio base address 00000000000d8000h ro 0170?0173h rp5d root port 5 descriptor 05xx0002h r/wo, ro 0178?017fh rp5a root port 5 base address 00000000000e4000h ro 0180?0183h rp6d root port 6 descriptor 06xx0002h r/wo, ro 0188?018fh rp6ba root port 6 base address 00000000000e5000h ro 01a0?01a3h ilcl internal link capability list 00010006h ro 01a4?01a7h lcap link capabilities 00012841h ro, r/wo 01a8?01a9h lctl link control 0000h r/w 01aa?01abh lsts link status 0041h ro 01f4-01f7h cir2 chipset initialization register 2 00000000h r/w 01fc-01fdh cir3 chipset initialization register 3 0000h r/w 0220-0223h bcr backbone configuration 00000000h r/w 0224?0227h rpc root port configuration 0000000yh r/w, ro 0234-0327h dmic dmi control 00000000h r/w, ro 0238?023bh rpfn root port function number for pci express root ports 00543210h r/wo, ro 0290-0293h fpss function level reset pending status summary 00000000h ro 0f20-0f23h cir13 chipset initialization register 13 b2b477cch r/w 1d40-1d47h cir5 chipset initialization register 5 0000000000000000h r/w 1e00?1e03h trsr trap status register 00000000h r/wc, ro 1e10?1e17h trcr trapped cycle register 0000000000000000h ro 1e18-1e1fh twdr trapped write data register 0000000000000000h ro 1e80-1e87h iotr0 i/o trap register 0 0000000000000000h r/w 1e88-1e8fh iotr1 i/o trap register 1 0000000000000000h r/w 1e90-1e97h iotr2 i/o trap register 2 0000000000000000h r/w table 10-1. chipset configuration register memory map (memory sp ace) (sheet 2 of 4) offset mnemonic register name default type http://www..net/ datasheet pdf - http://www..net/ datasheet 305 chipset configuration registers 1e98-1e9fh iotr3 i/o trap register 3 0000000000000000h r/w 2010-2013h dmc dmi miscellaneous control register 00000002h r/w 2034-2037h cir7 chipset initialization register 7 b2b477cch r/w 3000?3000h tctl tco control 00h r/w 3100?3103h d31ip device 31 interrupt pin 03243200h r/w, ro 3104?3107h d30ip device 30 interrupt pin 00000000h ro 3108?310bh d29ip device 29 interrupt pin 10004321h r/w 310c?310fh d28ip device 28 interrupt pin 00214321h r/w 3110?3113h d27ip device 27 interrupt pin 00000001h r/w 3114?3117h d26ip device 26 interrupt pin 30000321h r/w 3118?311bh d25ip device 25 interrupt pin 00000001h r/w 3140?3141h d31ir device 31 interrupt route 3210h r/w 3142?3143h d30ir device 30 interrupt route 0000h ro 3144?3145h d29ir device 29 interrupt route 3210h r/w 3146?3147h d28ir device 28 interrupt route 3210h r/w 3148?3149h d27ir device 27 interrupt route 3210h r/w 314c?314dh d26ir device 26 interrupt route 3210h r/w 3150?3151h d25ir device 25 interrupt route 3210h r/w 31fe?31ffh (corporate only) oic other interrupt control 0000h r/w 31ff?31ffh (consumer only) oic other interrupt control 00h r/w 3300-3303h sbemc3 scheduled break event c3 00000000h r/w 3304-3307h sbemc4 schedule break event c4 00000000h r/w 3310?3313h (corporate only) prsts power and reset status 3400?3403h rc rtc configuration 00000000h r/w, r/wlo 3404?3407h hptc high precision timer configuration 00000000h r/w 3410?3413h gcs general control and status 000000yy0h r/w, r/wlo 3414?3414h buc backed up control 00h r/w 3418?341bh fd function disable 00000000h r/w 341c?341fh cg clock gating 00000000h r/w 3420?3420h pdsw function disable sus well 00h r/w 3430-3433h cir8 chipset initialization register 8 00000000h r/w table 10-1. chipset configurat ion register memory map (mem ory space) (sheet 3 of 4) offset mnemonic register name default type http://www..net/ datasheet pdf - http://www..net/ chipset configuration registers 306 datasheet 10.1.1 vch?virtual channel capability header register offset address: 0000?0003h attribute: r/wo default value: 10010002h size: 32-bit 10.1.2 vcap1?virtual channel capability #1 register offset address: 0004?0007h attribute: ro, r/wo default value: 00000801h size: 32-bit 350c-350fh cir9 chipset initialization register 9 00000000h r/w 3524?3525h ppo usb port power off 0000h r/w 352c-352fh cir10 chipset initialization register 10 0008c008hh r/w 35f0-35f3h map usb remap control 00000000h r/wo table 10-1. chipset configuration register memory map (memory sp ace) (sheet 4 of 4) offset mnemonic register name default type bit description 31:20 next capability offset (nco) ? r/wo. indicates the next item in the list. 19:16 capability version (cv ) ? r/wo. indicates support as a version 1 capability structure. 15:0 capability id (cid) ? r/wo. indicates this is the virtual channel capability item. bit description 31:12 reserved 11:10 port arbitration tabl e entry size (pats) ? ro. indicates the size of the port arbitration table is 4 bits (to allow up to 8 ports). 9:8 reference clock (rc) ? ro. fixed at 100 ns. 7 reserved 6:4 low priority extended vc count (lpevc) ? ro. indicates that there are no additional vcs of low priority with extended capabilities. 3 reserved 2:0 extended vc count (evc) ? r/wo. indicates that there is one additional vc (vc1) that exists with extended capabilities. http://www..net/ datasheet pdf - http://www..net/ datasheet 307 chipset configuration registers 10.1.3 vcap2?virtual channe l capability #2 register offset address: 0008?000bh attribute: ro default value: 00000001h size: 32-bit 10.1.4 pvc?port virtual ch annel control register offset address: 000c?000dh attribute: ro, r/w default value: 0000h size: 16-bit 10.1.5 pvs?port virtual channel status register offset address: 000e?000fh attribute: ro default value: 0000h size: 16-bit bit description 31:24 vc arbitration table offset (ato) ? ro. indicates that no table is present for vc arbitration since it is fixed. 23:8 reserved 7:0 vc arbitration capability (ac) ? ro. indicates that the vc arbitration is fixed in the root complex. bit description 15:04 reserved 3:1 vc arbitration select (as) ? r/w. indicates which vc should be programmed in the vc arbitration table. the root complex ta kes no action on the setting of this field since there is no arbitration table. 0 load vc arbitration table (lat) ? ro. indicates that the table programmed should be loaded into the vc arbitration tabl e. this bit is define d as read/write with always returning 0 on reads. bit description 15:1 reserved 0 vc arbitration table status (vas) ? ro. indicates the coherency status of the vc arbitration table when it is being updated. this field is always 0 in the root complex since there is no vc arbitration table. http://www..net/ datasheet pdf - http://www..net/ chipset configuration registers 308 datasheet 10.1.6 v0cap?virtual channel 0 resource capability register offset address: 0010?0013h attribute: ro default value: 00000001h size: 32-bit 10.1.7 v0ctl?virtual channel 0 resource control register offset address: 0014?0017h attribute: r/w, ro default value: 800000ffh size: 32-bit bit description 31:24 port arbitration table offset (at) ? ro. this vc implements no port arbitration table since the arbitration is fixed. 23 reserved 22:16 maximum time slots (mts) ? ro. this vc implements fixed arbitration, and therefore this field is not used. 15 reject snoop transactions (rts) ? ro. this vc must be able to take snoopable transactions. 14 advanced packet switching (aps) ? ro. this vc is capable of all transactions, not just advanced packet switching transactions. 13:8 reserved 7:0 port arbitration capability (pac) ? ro. indicates that this vc uses fixed port arbitration. bit description 31 virtual channel enable (en) ? ro. always set to 1. vc 0 is always enabled and cannot be disabled. 30:27 reserved 26:24 virtual channel identifier (id) ? ro. indicates the id to use for this virtual channel. 23:20 reserved 19:17 port arbitration select (pas) ? r/w. indicates which port table is being programmed. the root complex takes no action on this setting since the arbitration is fixed and there is no arbitration table. 16 load port arbitration table (lat) ? ro. the root complex does not implement an arbitration table for this virtual channel. 15:8 reserved 7:1 transaction class / virtual channel map (tvm) ? r/w. indicates which transaction classes are mapped to this virt ual channel. when a bit is set, this transaction class is mapped to the virtual channel. 0 reserved http://www..net/ datasheet pdf - http://www..net/ datasheet 309 chipset configuration registers 10.1.8 v0sts?virtual channel 0 resource status register offset address: 001a?001bh attribute: ro default value: 0000h size: 16-bit 10.1.9 v1cap?virtual channel 1 resource capability register offset address: 001c?001fh attribute: r/wo, ro default value: 03008011h (consumer) size: 32-bit 00008001h (corporate) bit description 15:2 reserved 1 vc negotiation pending (np) ? ro. when set, indicates the virtual channel is still being negotiated wi th ingress ports. 0 port arbitration tables status (ats) ? ro. there is no port arbitration table for this vc, so this bit is reserved at 0. bit description 31:24 (corporate only) port arbitration table offset (at) ? ro. indicates the location of the port arbitration table in the root complex. a valu e of 0h indicates the table is not present 31:24 (consumer only) port arbitration table offset (at) ? ro. indicates the location of the port arbitration table in the root complex. a value of 3h indicates the table is at offset 30h. 23 reserved 22:16 maximum time slots (mts) ? r/wo. this value is u pdated by platform bios based upon the determin ation of the number of time slots available in the platform. 15 reject snoop transactions (rts) ? ro. all snoopable transactions on vc1 are rejected. this vc is for isochronous transfers only. 14 advanced packet switching (aps) ? ro. this vc is capable of all transactions, not just advanced packet switching transactions. 13:8 reserved 7:0 (corporate only) port arbitration capability (pac) ? ro. indicates the port arbitration capability is hardware-fixed. 7:0 (consumer only) port arbitration capability (pac) ? ro. indicates the port arbitration capability is time-based wrr of 128 phases. http://www..net/ datasheet pdf - http://www..net/ chipset configuration registers 310 datasheet 10.1.10 v1ctl?virtual channel 1 resource control register offset address: 0020?0023h attribute: r/w, ro default value: 00000000h (consumer) size: 32-bit 00000000h (corporate) 10.1.11 v1sts?virtual channel 1 resource status register offset address: 0026?0027h attribute: ro default value: 0000h size: 16-bit bit description 31 virtual channel enable (en) ? r/w. enables the vc when set. disables the vc when cleared. 30:27 reserved 26:24 virtual channel identifier (id) ? r/w. indicates the id to use for this virtual channel. 23:20 reserved 19:17 (corporate only) port arbitration select (pas) ?ro. the only permissible value of this field is 0h for fixed arbitration. 19:17 (consumer only) port arbitration select (pas) ? r/w. indicates which port table is being programmed. the only permissible value of this field is 4h fo r the time-based wrr entries. 16 (corporate only) reserved 16 (consumer only) load port arbitration table (lat) ? r/w. when set, the port arbitration table loaded based upon the pas field in this register. this bit al ways returns 0 when read. 15:8 reserved 7:1 transaction class / virtual channel map (tvm) ? r/w. indicates which transaction classes are mapped to this virtual channel. when a bit is set, this transaction class is mapped to the virtual channel. 0reserved bit description 15:2 reserved 1 vc negotiation pending (np) ? ro. when set, indicates the virtual channel is still being negotiated wi th ingress ports. 0 port arbitration tables status (ats) ? ro. indicates the coherency status of the port arbitration table. this bit is set when lat (offset 000 ch:bit 0) is written with value 1 and pas (offset 0014h:bits19:17) has value of 4h. this bit is cleared after the table has been updated. http://www..net/ datasheet pdf - http://www..net/ datasheet 311 chipset configuration registers 10.1.12 pat?port arbitratio n table (consumer only) offset address: 0030-006fh attribute: default value: size: 64-byte this a 64-byte register that contains the ar bitration table to be loaded into the port arbitration table. every 4-bits contains an entry for one of the downstream pci express* ports or a 0h to indicate idle. the ports are mapped as follows: ? port 1: value used is 1h. ? port 2: value used is 2h. ? port 3: value used is 3h. ? port 4: value used is 4h. ? port 5: value used is 5h. ? port 6: value used is 6h. ? intel high definition audio: value used is fh. 10.1.13 cir1?chipset init ialization register 1 offset address: 0088?008bh attribute: r/wo default value: 00000000h size: 32-bit 10.1.14 rec?root erro r command register offset address: 00ac?00afh attribute: r/w default value: 0000h size: 32-bit bit description 31:21 reserved 20 cir1 field 3 ? r/wo. bios must set this bit. 19:16 reserved 15 cir1 field 2 ? r/wo. bios must set this bit. 14:13 reserved 12 cir1 field 1 ? r/wo. bios must set this bit. 11:0 reserved bit description 31 drop poisoned downstream packets (dpdp) ? r/w. determines how downstream packets on dmi are handled that are received with the ep field set, indicating poisoned data: 1: this packet and all subseq uent packets with data receiv ed on dmi for any vc will have their unsupported transaction (ut) field set causing them to master abort downstream. packets without data such as memory, io and config read requests are allowed to proceed. 0: packets are forwarded downstream without forcing the ut field set. 30:0 reserved http://www..net/ datasheet pdf - http://www..net/ chipset configuration registers 312 datasheet 10.1.15 rctcl?root complex topolo gy capabilities list register offset address: 0100?0103h attribute: ro default value: 1a010005h size: 32-bit 10.1.16 esd?element self description register offset address: 0104?0107h attribute: r/wo, ro default value: 00000802h size: 32-bit 10.1.17 uld?upstream link descriptor register offset address: 0110?0113h attribute: r/wo, ro default value: 00000001h size: 32-bit bit description 31:20 next capability (next) ? ro. indicates the next item in the list. 19:16 capability version (cv) ? ro. indicates the version of the capability structure. 15:0 capability id (cid) ? ro. indicates this is a pci expr ess* link capability section of an rcrb. bit description 31:24 port number (pn) ? ro. a value of 0 to indicate the egress port for the intel ich10. 23:16 component id (cid) ? r/wo. indicates the component id assigned to this element by software. this is written once by platform bios and is locked until a platform reset. 15:8 number of link entries (nle) ? ro. indicates that one link entry (corresponding to dmi), 6 root port entries (for the downst ream ports), an d the intel high definition audio device are desc ribed by this rcrb. 7:4 reserved 3:0 element type (et) ? ro. indicates that the element type is a root complex internal link. bit description 31:24 target port number (pn) ? r/wo. this field is prog rammed by platform bios to match the port number of the (g)mch rc rb that is attached to this rcrb. 23:16 target component id (tcid) ? r/wo. this field is prog rammed by platform bios to match the component id of the (g)mch rcrb that is attached to this rcrb. 15:2 reserved 1 link type (lt) ? ro. indicates that the link points to the (g)mch rcrb. 0 link valid (lv) ? ro. indicates that the link entry is valid. http://www..net/ datasheet pdf - http://www..net/ datasheet 313 chipset configuration registers 10.1.18 ulba?upstream link base address register offset address: 0118?011fh attribute: r/wo default value: 0000000000000000h size: 64-bit 10.1.19 rp1d?root port 1 descriptor register offset address: 0120?0123h attribute: r/wo, ro default value: 01xx0002h size: 32-bit 10.1.20 rp1ba?root port 1 base address register offset address: 0128?012fh attribute: ro default value: 00000000000e0000h size: 64-bit bit description 63:32 base address upper (bau) ? r/wo. this field is progra mmed by platform bios to match the upper 32-bits of base address of the (g)mch rcrb that is attached to this rcrb. 31:0 base address lower (bal) ? r/wo. this field is programmed by platform bios to match the lower 32-bits of base address of the (g)mch rcrb that is attached to this rcrb. bit description 31:24 target port number (pn) ? ro. indicates the target port number is 1h (root port #1). 23:16 target component id (tcid) ? r/wo. this field returns the value of the esd.cid (offset 0104h, bits 23:16) field programmed by platform bios, sinc e the root port is in the same component as the rcrb. 15:2 reserved 1 link type (lt) ? ro. indicates that the li nk points to a root port. 0 link valid (lv) ? ro. when fd.pe1d (offset 3418h, bit 16) is set, this link is not valid (returns 0). when fd.pe1d is cleared, this link is valid (returns 1). bit description 63:28 reserved 27:20 bus number (bn) ? ro. indicates the root port captured bus number. 19:15 device number (dn) ? ro. indicates the root port is on device #28. 14:12 function number (fn) ? ro. indicates the root port is on function #0. 11:0 reserved http://www..net/ datasheet pdf - http://www..net/ chipset configuration registers 314 datasheet 10.1.21 rp2d?root port 2 descriptor register offset address: 0130?0133h attribute: r/wo, ro default value: 02xx0002h size: 32-bit 10.1.22 rp2ba?root port 2 base address register offset address: 0138?013fh attribute: ro default value: 00000000000e1000h size: 64-bit 10.1.23 rp3d?root port 3 descriptor register offset address: 0140?0143h attribute: r/wo, ro default value: 03xx0002h size: 32-bit bit description 31:24 target port number (pn) ? ro. indicates the target port number is 2h (root port #2). 23:16 target component id (tcid) ? r/wo. this field returns the value of the esd.cid (offset 0104h, bits 23:16) field programmed by platform bios, since the root port is in the same component as the rcrb. 15:2 reserved 1 link type (lt) ? ro. indicates that the link points to a root port. 0 link valid (lv) ? ro. when rpc.pc (offset 0224h, bits 1:0) is ?01?, ?10?, or ?11?, or fd.pe2d (offset 3418h, bit 17) is set, the link for this root port is not valid (return 0). when rpc.pc is ?00? and fd.pe2 d is cleared, the link for this root port is valid (return 1). bit description 63:28 reserved 27:20 bus number (bn) ? ro. indicates the root port captured bus number. 19:15 device number (dn) ? ro. indicates the root port is on device #28. 14:12 function number (fn) ? ro. indicates the root port is on function #1. 11:0 reserved bit description 31:24 target port number (pn) ? ro. indicates the target port number is 3h (root port #3). 23:16 target component id (tcid) ? r/wo. this field returns the value of the esd.cid (offset 0104h, bits 23:16) field programmed by platform bios, since the root port is in the same component as the rcrb. 15:2 reserved 1 link type (lt) ? ro. indicates that the link points to a root port. 0 link valid (lv) ? ro. when rpc.pc (offset 0224h, bits 1:0) is ?11?, or fd.pe3d (offset 3418h, bit 18) is set, the link for th is root port is not valid (return 0). when rpc.pc is ?00?, ?01?, or ?10?, and fd.pe3d is cl eared, the link for this root port is valid (return 1). http://www..net/ datasheet pdf - http://www..net/ datasheet 315 chipset configuration registers 10.1.24 rp3ba?root port 3 base address register offset address: 0148?014fh attribute: ro default value: 00000000000e2000h size: 64-bit 10.1.25 rp4d?root port 4 descriptor register offset address: 0150?0153h attribute: r/wo, ro default value: 04xx0002h size: 32-bit 10.1.26 rp4ba?root port 4 base address register offset address: 0158?015fh attribute: ro default value: 00000000000e3000h size: 64-bit bit description 63:28 reserved 27:20 bus number (bn) ? ro. indicates the root port captured bus number. 19:15 device number (dn) ? ro. indicates the root port is on device #28. 14:12 function number (fn) ? ro. indicates the root port is on function #2. 11:0 reserved bit description 31:24 target port number (pn) ? ro. indicates the target port number is 4h (root port #4). 23:16 target component id (tcid) ? r/wo. this field returns the value of the esd.cid (offset 0104h, bits 23:16) field programmed by platform bios, sinc e the root port is in the same component as the rcrb. 15:2 reserved 1 link type (lt) ? ro. indicates that the link points to a root port. 0 link valid (lv) ? ro. when rpc.pc (offset 0224h, bits 1:0) is ?10? or ?11?, or fd.pe4d (offset 3418h, bit 19) is set, the link for this root port is not valid (return 0). when rpc.pc is ?00? or ?01? and fd.pe4d is cleared, the link for this root port is valid (return 1). bit description 63:28 reserved 27:20 bus number (bn) ? ro. indicates the root port captured bus number. 19:15 device number (dn) ? ro. indicates the root port is on device #28. 14:12 function number (fn) ? ro. indicates the root port is on function #3. 11:0 reserved http://www..net/ datasheet pdf - http://www..net/ chipset configuration registers 316 datasheet 10.1.27 hdd?intel ? high definition audi o descriptor register offset address: 0160?0163h attribute: r/wo, ro default value: 0fxx0002h size: 32-bit 10.1.28 hdba?intel ? high definition audi o base address register offset address: 0168?016fh attribute: ro default value: 00000000000d8000h size: 64-bit 10.1.29 rp5d?root port 5 descriptor register offset address: 0170?0173h attribute: r/wo, ro default value: 05xx0002h size: 32-bit bit description 31:24 target port number (pn) ? ro. indicates the target port number is 15h (intel high definition audio). 23:16 target component id (tcid) ? r/wo. this field returns the value of the esd.cid (offset 0104h, bits 23:16) field programmed by platform bios, since the root port is in the same component as the rcrb. 15:2 reserved 1 link type (lt) ? ro. indicates that the link points to a root port. 0 link valid (lv) ? ro. when fd.zd (offset 3418h, bit 4) is set, the link to intel high definition audio is not valid (return 0). when fd.zd is cleared, the link to intel high definition audio is valid (return 1). bit description 63:28 reserved 27:20 bus number (bn) ? ro. indicates the high definition audio captured bus number. 19:15 device number (dn) ? ro. indicates the root port is on device #27. 14:12 function number (fn) ? ro. indicates the root port is on function #0. 11:0 reserved bit description 31:24 target port number (pn) ? ro. indicates the target port number is 5h (root port #5). 23:16 target component id (tcid) ? r/wo. this field returns the value of the esd.cid (offset 0104h, bits 23:16) field programmed by platform bios, since the root port is in the same component as the rcrb. 15:2 reserved 1 link type (lt) ? ro. indicates that the link points to a root port. 0 link valid (lv) ? ro. when fd.pe5d (offs et 3418h, bit 20) is set, the link for this root port is not valid (return 0). when fd.pe5d is cleared, th e link for this root port is valid (return 1). http://www..net/ datasheet pdf - http://www..net/ datasheet 317 chipset configuration registers 10.1.30 rp5ba?root port 5 base address register offset address: 0178?017fh attribute: ro default value: 00000000000e4000h size: 64-bit 10.1.31 rp6d?root port 6 descriptor register offset address: 0180?0183h attribute: r/wo, ro default value: 06xx0002h size: 32-bit 10.1.32 rp6ba?root port 6 base address register offset address: 0188?018fh attribute: ro default value: 00000000000e5000h size: 64-bit bit description 63:28 reserved 27:20 bus number (bn) ? ro. indicates the root port captured bus number. 19:15 device number (dn) ? ro. indicates the root port is on device #28. 14:12 function number (fn) ? ro. indicates the root port is on function #4. 11:0 reserved bit description 31:24 target port number (pn) ? ro. indicates the target port number is 6h (root port #6). 23:16 target component id (tcid) ? r/wo. this field returns the value of the esd.cid (offset 0104h, bits 23:16) field programmed by platform bios, sinc e the root port is in the same component as the rcrb. 15:2 reserved 1 link type (lt) ? ro. indicates that the li nk points to a root port. 0 link valid (lv) ? ro. when rpc.pc2 (offset 0224h, bits 1:0) is ?01? or fd.pe6d (offset 3418h, bit 21) is set, the link for this root port is not valid (return 0). when rpc.pc is ?00? and fd.pe6d is cleared, the li nk for this root port is valid (return 1). bit description 63:28 reserved 27:20 bus number (bn) ? ro. indicates the root port captured bus number. 19:15 device number (dn) ? ro. indicates the root port is on device #28. 14:12 function number (fn) ? ro. indicates the root port is on function #5. 11:0 reserved http://www..net/ datasheet pdf - http://www..net/ chipset configuration registers 318 datasheet 10.1.33 ilcl?internal link ca pabilities li st register offset address: 01a0?01a3h attribute: ro default value: 00010006h size: 32-bit 10.1.34 lcap?link capa bilities register offset address: 01a4?01a7h attribute: r/wo, ro default value: 00012841h size: 32-bit 10.1.35 lctl?link control register offset address: 01a8?01a9h attribute: r/w default value: 0000h size: 16-bit bit description 31:20 next capability offset (next) ? ro. indicates this is the last item in the list. 19:16 capability version (cv) ? ro. indicates the version of the capability structure. 15:0 capability id (cid) ? ro. indicates this is capability for dmi. bit description 31:18 reserved 17:15 reserved 14:12 l0s exit latency (el0) ? r/wo. this field indicates that exit latency is 128 ns to less than 256 ns. 11:10 active state link pm support (apms) ? r/wo. indicates that l0s and l1 are supported on dmi. 9:4 maximum link width (mlw) ? ro. indicates the maximum link width is 4 ports. 3:0 maximum link speed (mls) ? ro. indicates the link speed is 2.5 gb/s. bit description 15:8 reserved 7 extended synch (es) ? r/w. when set, forces ex tended transmission of fts ordered sets when exiting l0s prior to entering l0. 6:2 reserved 1:0 active state link pm control (aspm) ? r/w. indicates whether dmi should enter l0s. 00 = disabled 01 = l0s entry enabled 10 = reserved 11 = reserved corporate only: the value of this register is used unless the dmi aspm override enable register is set, in which ca se the dmi aspm override is used. http://www..net/ datasheet pdf - http://www..net/ datasheet 319 chipset configuration registers 10.1.36 lsts?link status register offset address: 01aa?01abh attribute: ro default value: 0041h size: 16-bit 10.1.37 cir2 ? chipset init ialization register 2 offset address: 01f4?01f7h attribute: r/w default value: 00000000h size: 32-bit 10.1.38 cir3 ? chipset init ialization register 3 offset address: 01fc?01fdh attribute: r/w default value: 0000h size: 16-bit 10.1.39 bcr ? backbone co nfiguration register offset address: 0220?0223h attribute: r/w default value: 00000000h size: 32-bit bit description 15:10 reserved 9:4 negotiated link width (nlw) ? ro. negotiated link width is x4 (000100b). 3:0 link speed (ls) ? ro. link is 2.5 gb/s. bit description 31:0 cir2 field 1 ? r/w. bios shall program to 86000040h bit description 15:11 reserved 10:8 cir3 field 3 ? r/w. bios must program this field to 110b. 7:4 reserved 3 cir3 field 2 ? r/w. bios must set this bit. 2 reserved 1:0 cir3 field 1 ? r/w. bios must program this field to 11b. bit description 31:7 reserved 6 bcr field 2 ? r/w. bios must set this bit. 5:3 reserved 2:0 bcr field 1 ? r/w. bios program this field to 101b http://www..net/ datasheet pdf - http://www..net/ chipset configuration registers 320 datasheet 10.1.40 rpc?root port configuration register offset address: 0224?0227h attribute: r/w, ro default value: 0000000yh (y = 00xxb) size: 32-bit bit description 31:8 reserved 7 high priority port enable (hpe) ? r/w. 0 = the high priority path is not enabled. 1 = the port selected by the hpp field in this register is enabled for high priority. it will be arbitrated above all other vc0 (including integrated vc0) devices. 6:4 high priority port (hpp) ? r/w. this controls whic h port is enabled for high priority when the hpe bit in this register is set. 111 = reserved 110 = reserved 101 = port 6 100 = port 5 101 = port 4 010 = port 3 001 = port 2 000 = port 1 3 reserved 2 port configuration2 (pc2) ? ro. this controls how the pci bridges are organized in various modes of operation for ports 5 and 6. corporate only: this bit is set by the pciepcs2[1:0] soft strap. 1 = reserved 0 = 2 x1s, port 5 (x1), port 6 (x1) this bit is in the resume well and is only reset by rsmrst#. 1:0 port configuration (pc) ? ro. this controls how the pci bridges are organized in various modes of operation for ports 1-4. for the following mappings, if a port is not shown, it is considered a x1 port with no connection. consumer only: these bits represent the strap values of hda_sdout (bit 1) and hda_sync (bit 0) when tp[3] is not pull ed low at the rising edge of pwrok. corporate only: these bits are set by the pciepcs1[1:0] soft strap. 11 = 1 x4, port 1 (x4) 10 = reserved 01 = reserved 00 = 4 x1s, port 1 (x1), port 2 (x1), port 3 (x1) and port 4 (x1) these bits are in the resume well and are only reset by rsmrst#. http://www..net/ datasheet pdf - http://www..net/ datasheet 321 chipset configuration registers 10.1.41 dmic?dmi control register offset address: 0234?0237h attribute: r/w default value: 00000000h size: 32-bit 10.1.42 rpfn?root port function number and hide for pci express* root ports offset address: 0238?023ch attribute: r/wo, ro default value: 00543210h size: 32-bit for the pci express root ports, the assignment of a function number to a root port is not fixed. bios may re-assign the function numbers on a port by port basis. this capability will allow bios to disable/hide any root port and still have functions 0 thru n- 1 where n is the total number of enabled root ports. port numbers will remain fixed to a physical root port. the existing root port function disable registers operate on physical ports (not functions). port configuration (1x4, 4x1, etc.) is no t affected by the logical function number assignment and is associated with physical ports. bit description 31:19 reserved 18 corporate only aspm control override enable (aspmcoen) ? rw. 1 = dmi will use the values in th e aspm control override registers 0 = dmi will use the aspm register s in the link control register. notes: this register allows bios to control the dmi aspm settings instead of the os. 18 (consumer only) reserved 17:16 (corporate only) aspm control override (aspmo) ? rw. provides bios control of whether dmi should enter l0s or l1 or both. 00 = disabled 01 = l0s entry enabled 10 = l1 entry enabled 11 = l0s and l1 entry enabled. 17:16 (consumer only) reserved 15:2 reserved 1:0 dmi clock gate enable (dmicgen) ? r/w. bios must program this field to 11b. http://www..net/ datasheet pdf - http://www..net/ chipset configuration registers 322 datasheet bit description 31:24 reserved 23 root port 6 config hide (rp6ch) ? rw. this bit is used to hide the root port and any devices behind it from bein g discovered by the os. when set to ?1? the root port will not claim any downstream configuration transactions. 22:20 root port 6 function number (rp6fn) ? r/wo. these bits set the function number for pci express root port 6. this root port function number must be a unique value from the other r oot port function numbers 19 root port 5 config hide (rp5ch) ? rw. this bit is used to hide the root port and any devices behind it from bein g discovered by the os. when set to ?1? the root port will not claim any downstream configuration transactions. 18:16 root port 5 function number (rp5fn) ? r/wo. these bits set the function number for pci express root port 5. this root port function number must be a unique value from the other r oot port function numbers 15 root port 4 config hide (rp4ch) ? rw. this bit is used to hide the root port and any devices behind it from bein g discovered by the os. when set to ?1? the root port will not claim any downstream configuration transactions. 14:12 root port 4 function number (rp4fn) ? r/wo. these bits set the function number for pci express root port 4. this root port function number must be a unique value from the other r oot port function numbers 11 root port 3 config hide (rp3ch) ? rw. this bit is used to hide the root port and any devices behind it from bein g discovered by the os. when set to ?1? the root port will not claim any downstream configuration transactions. 10:8 root port 3 function number (rp3fn) ? r/wo. these bits set the function number for pci express root port 3. this root port function number must be a unique value from the other r oot port function numbers 7 root port 2 config hide (rp2ch) ? rw. this bit is used to hide the root port and any devices behind it from bein g discovered by the os. when set to ?1? the root port will not claim any downstream configuration transactions. 6:4 root port 2 function number (rp2fn) ? r/wo. these bits set the function number for pci express root port 2. this root port function number must be a unique value from the other r oot port function numbers 3 root port 1 config hide (rp1ch) ? rw. this bit is used to hide the root port and any devices behind it from bein g discovered by the os. when set to ?1? the root port will not claim any downstream configuration transactions. 2:0 root port 1 function number (rp1fn) ? r/wo. these bits set the function number for pci express root port 1. this root port function number must be a unique value from the other r oot port function numbers http://www..net/ datasheet pdf - http://www..net/ datasheet 323 chipset configuration registers 10.1.43 flrstat?flr pend ing status register offset address: 0290?0293h attribute: ro default value: 00000000h size: 32-bit bit description 31:24 reserved. 23 flr pending status for d29:f7, ehci #1 ? r0. 0 = function level reset is not pending. 1 = function level reset is pending. 22:20 reserved. 19 flr pending status for d29:f3, uhci #6 ? r0. 0 = function level reset is not pending. 1 = function level reset is pending. 18 flr pending status for d29:f2, uhci #3 ? r0. 0 = function level reset is not pending. 1 = function level reset is pending. 17 flr pending status for d29:f1, uhci #2 ? r0. 0 = function level reset is not pending. 1 = function level reset is pending. 16 flr pending status for d29:f0, uhci #1 ? r0. 0 = function level reset is not pending. 1 = function level reset is pending. 15 flr pending status for d26:f7, ehci #2 ? r0. 0 = function level reset is not pending. 1 = function level reset is pending. 14:11 reserved. 10 flr pending status for d26:f2, uhci #6 ? r0. 0 = function level reset is not pending. 1 = function level reset is pending. 9 flr pending status for d26:f1, uhci #5 ? r0. 0 = function level reset is not pending. 1 = function level reset is pending. 8 flr pending status for d26:f0, uhci #4 ? r0. 0 = function level reset is not pending. 1 = function level reset is pending. 7:0 reserved. http://www..net/ datasheet pdf - http://www..net/ chipset configuration registers 324 datasheet 10.1.44 cir13?chipset initialization register 13 offset address: 0f20h?0f23h attribute: r/w default value: b2b477cch size: 32-bit 10.1.45 cir5?chipset init ialization register 5 offset address: 1d40h?1d47h attribute: r/w default value: 0000000000000000h size: 64-bit 10.1.46 trsr?trap status register offset address: 1e00?1e03h attribute: r/wc, ro default value: 00000000h size: 32-bit bit description 31:20 reserved 19:16 cir13 field 1 ? r/w. bios must program this field to 0101b. 15:0 reserved bit description 63:1 reserved 0 cir5 field 1 ? r/w. bios must program this field to 1b. bit description 31:4 reserved 3:0 cycle trap smi# status (ctss) ? r/wc. these bits are set by hardware when the corresponding cycle trap register is enable d and a matching cycle is received (and trapped). these bits are or?ed together to create a single status bit in the power management register space. note that the smi# and trapping must be enabled in order to set these bits. these bits are set before the completion is generated for the trapped cycle, thereby ensuring that the processor can enter the smi# handler wh en the instruction completes. each status bit is cleared by writing a 1 to th e corresponding bit location in this register. http://www..net/ datasheet pdf - http://www..net/ datasheet 325 chipset configuration registers 10.1.47 trcr?trapped cycle register offset address: 1e10?1e17h attribute: ro default value: 0000000000000000h size: 64-bit this register saves information about the i/o cycle that was trapped and generated the smi# for software to read. 10.1.48 twdr?trapped write data register offset address: 1e18?1e1fh attribute: ro default value: 0000000000000000h size: 64-bit this register saves the data from i/o write cycles that are trapped for software to read. bit description 63:25 reserved 24 read/write# (rwi) ? ro. 0 = trapped cycle was a write cycle. 1 = trapped cycle was a read cycle. 23:20 reserved 19:16 active-high byte enables (ahbe) ? ro. this is the dword-aligned byte enables associated with the trapped cycle. a 1 in any bit location indicates that the corresponding byte is enabled in the cycle. 15:2 trapped i/o address (tioa) ? ro. this is the dword-aligned address of the trapped cycle. 1:0 reserved bit description 63:32 reserved 31:0 trapped i/o data (tiod) ? ro. dword of i/o write data. this field is undefined after trapping a read cycle. http://www..net/ datasheet pdf - http://www..net/ chipset configuration registers 326 datasheet 10.1.49 iotrn ? i/o trap register (0-3) offset address: 1e80?1e87h register 0 attribute: r/w 1e88?1e8fh register 1 1e90?1e97h register 2 1e98?1e9fh register 3 default value: 0000000000000000h size: 64-bit these registers are used to specify the set of i/o cycles to be trapped and to enable this functionality. bit description 63:50 reserved 49 read/write mask (rwm) ? r/w. 0 = the cycle must match the type specified in bit 48. 1 = trapping logic will operate on both read and write cycles. 48 read/write# (rwio) ? r/w. 0 = write 1 = read note: the value in this field does not matter if bit 49 is set. 47:40 reserved 39:36 byte enable mask (bem) ? r/w. a 1 in any bit position indicates that any value in the corresponding byte enable bit in a receiv ed cycle will be treated as a match. the corresponding bit in the byte en ables field, below, is ignored. 35:32 byte enables (tbe) ? r/w. active-high dword-aligned byte enables. 31:24 reserved 23:18 address[7:2] mask (adma) ? r/w. a 1 in any bit position indicates that any value in the corresponding address bit in a receiv ed cycle will be treated as a match. the corresponding bit in the addres s field, below, is ignored. the mask is only provided for the lower 6 bits of the dword address, al lowing for traps on address ranges up to 256 bytes in size. 17:16 reserved 15:2 i/o address[15:2] (ioad) ? r/w. dword-aligned address 1 reserved 0 trap and smi# enable (trse) ? r/w. 0 = trapping and smi# logic disabled. 1 = the trapping logic specified in this register is enabled. http://www..net/ datasheet pdf - http://www..net/ datasheet 327 chipset configuration registers 10.1.50 dmc?dmi miscellaneous control register offset address: 2010?2013h attribute: r/w default value: 00000002h size: 32-bit 10.1.51 cir6?chipset init ialization register 6 offset address: 2024?2027h attribute: r/w default value: 0b4030c0h size: 32-bit 10.1.52 cir7?chipset init ialization register 7 offset address: 2034?2037h attribute: r/w default value: b2b477cch size: 32-bit bit description 31:20 reserved 19 dmi misc. control field 1 ? r/w. bios shall always pr ogram this field as per the bios specification. 0 = disable dmi power savings. 1 = enable dmi power savings. 18:0 reserved bit description 31:8 reserved 7 cir6 field 1 ? r/w. bios must clear this bit. 6:0 reserved bit description 31:20 reserved 19:16 cir7 field 1 ? r/w. bios must program this field to 0101b. 15:0 reserved http://www..net/ datasheet pdf - http://www..net/ chipset configuration registers 328 datasheet 10.1.53 tctl?tco configuration register offset address: 3000?3000h attribute: r/w default value: 00h size: 8-bit bit description 7 tco irq enable (ie) ? r/w. 0 = tco irq is disabled. 1 = tco irq is enabled, as sele cted by the tco_irq_sel field. 6:3 reserved 2:0 tco irq select (is) ? r/w. specifies on which irq the tco will internally appear. if not using the apic, the tco interrupt must be routed to irq9-11, and that interrupt is not sharable with the serirq stream, but is shar eable with other pci interrupts. if using the apic, the tco interrupt can also be mapped to irq20-23, and can be shared with other interrupt. 000 = irq 9 001 = irq 10 010 = irq 11 011 = reserved 100 = irq 20 (only if apic enabled) 101 = irq 21 (only if apic enabled) 110 = irq 22 (only if apic enabled) 111 = irq 23 (only if apic enabled) when setting the these bits, the ie bit should be cleared to prevent glitching. when the interrupt is mapped to apic interrupts 9, 10 or 11, the apic should be programmed for active-high reception. when the interrupt is mapped to apic interrupts 20 through 23, the apic should be programmed for active-low reception. http://www..net/ datasheet pdf - http://www..net/ datasheet 329 chipset configuration registers 10.1.54 d31ip?device 31 in terrupt pi n register offset address: 3100?3103h attribute: r/w, ro default value: 03243200h size: 32-bit bit description 31:28 reserved 27:24 thermal throttle pin (ttip) ? r/w. indicates which pin the thermal throttle controller drives as its interrupt 0h = no interrupt 1h = inta# 2h = intb# (default) 3h = intc# 4h = intd# 5h?fh = reserved 23:20 sata pin 2 (sip2) ? r/w. indicates which pin the sa ta controller 2 drives as its interrupt. 0h = no interrupt 1h = inta# 2h = intb# (default) 3h = intc# 4h = intd# 5h?fh = reserved 19:16 reserved 15:12 smbus pin (smip) ? r/w. indicates which pin the smbus controller drives as its interrupt. 0h = no interrupt 1h = inta# 2h = intb# (default) 3h = intc# 4h = intd# 5h?fh = reserved 11:8 sata pin (sip) ? r/w. indicates which pin the sata controller drives as its interrupt. 0h = no interrupt 1h = inta# 2h = intb# (default) 3h = intc# 4h = intd# 5h?fh = reserved 7:4 reserved 3:0 lpc bridge pin (lip) ? ro. currently, the lp c bridge does not generate an interrupt, so this field is read-only and 0. http://www..net/ datasheet pdf - http://www..net/ chipset configuration registers 330 datasheet 10.1.55 d30ip?device 30 in terrupt pin register offset address: 3104?3107h attribute: ro default value: 00000000h size: 32-bit 10.1.56 d29ip?device 29 in terrupt pin register offset address: 3108?310bh attribute: r/w default value: 10004321h size: 32-bit bit description 31:4 reserved 3:0 pci bridge pin (pip) ? ro. currently, the pc i bridge does not generate an interrupt, so this field is read-only and 0. bit description 31:28 ehci pin (eip) ? r/w. indicates which pin the eh ci controller #1 drives as its interrupt. 0h = no interrupt 1h = inta# (default) 2h = intb# 3h = intc# 4h = intd# 5h-7h = reserved 27:16 reserved 15:12 uhci #6 pin (u3p) ? r/w. indicates which pin the uhci controller #6 (device 29 function 3) drives as its in terrupt, if controller exists 0h = no interrupt 1h = inta# 2h = intb# 3h = intc# 4h = intd# (default) 5h-7h = reserved note: this field should be set to 0h when uhci controller #6 remap bit (rcba offset 35f0h:bit 0) is set to 0. 11:8 uhci #3 pin (u2p) ? r/w. indicates which pin the uhci controller #3 (device 29 function 2) drives as its interrupt. 0h = no interrupt 1h = inta# 2h = intb# 3h = intc# (default) 4h = intd# 5h-7h = reserved http://www..net/ datasheet pdf - http://www..net/ datasheet 331 chipset configuration registers 10.1.57 d28ip?device 28 in terrupt pi n register offset address: 310c?310fh attribute: r/w default value: 00214321h size: 32-bit 7:4 uhci #2 pin (u1p) ? r/w. indicates which pin the uhci controller #2 (device 29 function 1) drives as its interrupt. 0h = no interrupt 1h = inta# 2h = intb# (default) 3h = intc# 4h = intd# 5h-7h = reserved 3:0 uhci #1 pin (u0p) ? r/w. indicates which pin the uhci controller #1 (device 29 function 0) drives as its interrupt. 0h = no interrupt 1h = inta# (default) 2h = intb# 3h = intc# 4h = intd# 5h-7h = reserved bit description bit description 31:16 reserved 23:20 pci express* #6 pin (p6ip) ? r/w. indicates which pin the pci express* port #6 drives as its interrupt. 0h = no interrupt 1h = inta# 2h = intb# (default) 3h = intc# 4h = intd# 5h-7h = reserved 19:16 pci express #5 pin (p5ip) ? r/w. indicates which pin the pci express port #5 drives as its interrupt. 0h = no interrupt 1h = inta# (default) 2h = intb# 3h = intc# 4h = intd# 5h-7h = reserved 15:12 pci express #4 pin (p4ip) ? r/w. indicates which pin the pci express* port #4 drives as its interrupt. 0h = no interrupt 1h = inta# 2h = intb# 3h = intc# 4h = intd# (default) 5h-7h = reserved http://www..net/ datasheet pdf - http://www..net/ chipset configuration registers 332 datasheet 10.1.58 d27ip?device 27 in terrupt pin register offset address: 3110?3113h attribute: r/w default value: 00000001h size: 32-bit 11:8 pci express #3 pin (p3ip) ? r/w. indicates which pi n the pci express port #3 drives as its interrupt. 0h = no interrupt 1h = inta# 2h = intb# 3h = intc# (default) 4h = intd# 5h-7h = reserved 7:4 pci express #2 pin (p2ip) ? r/w. indicates which pi n the pci express port #2 drives as its interrupt. 0h = no interrupt 1h = inta# 2h = intb# (default) 3h = intc# 4h = intd# 5h-7h = reserved 3:0 pci express #1 pin (p1ip) ? r/w. indicates which pi n the pci express port #1 drives as its interrupt. 0h = no interrupt 1h = inta# (default) 2h = intb# 3h = intc# 4h = intd# 5h-7h = reserved bit description bit description 31:4 reserved 3:0 intel ? high definition audio pin (zip) ? r/w. indicates whic h pin the intel high definition audio controller drives as its interrupt. 0h = no interrupt 1h = inta# (default) 2h = intb# 3h = intc# 4h = intd# 5h-fh = reserved http://www..net/ datasheet pdf - http://www..net/ datasheet 333 chipset configuration registers 10.1.59 d26ip?device 26 in terrupt pi n register offset address: 3114?3117h attribute: r/w default value: 30000321h size: 32-bit bit description 31:28 ehci #2 pin (e2ip) ? r/w. indicates which pin the ehci controller #2 drives as its interrupt: 0h = no interrupt 1h = inta# 2h = intb# 3h = intc# (default) 4h = intd# 5h-fh = reserved 27:12 reserved 11:8 uhci #6 pin (u2p) ? r/w. indicates which pin uhci controller #6 (device 26 function 2) drives as its interrupt, if controller exists. 0h = no interrupt 1h = inta# 2h = intb# 3h = intc# (default) 4h = intd# 5h-fh = reserved note: this field should be set to 0h when uhci contro ller #6 remap bit (rcba offset 35f0h:bit 0) is set to 1. 7:4 uhci #5 pin (u1p) ? r/w. indicates which pin uhci controller #5 (device 26 function 1), drives as its interrupt. 0h = no interrupt 1h = inta# 2h = intb# (default) 3h = intc# 4h = intd# 5h-fh = reserved 3:0 uhci #4 pin (u0p) ? r/w. indicates which pin uhci controller #4 (device 26 function 0), drives as its interrupt. 0h = no interrupt 1h = inta# (default) 2h = intb# 3h = intc# 4h = intd# 5h-fh = reserved http://www..net/ datasheet pdf - http://www..net/ chipset configuration registers 334 datasheet 10.1.60 d25ip?device 25 in terrupt pin register offset address: 3118?311bh attribute: r/w default value: 00000001h size: 32-bit 10.1.61 d31ir?device 31 in terrupt route register offset address: 3140?3141h attribute: r/w default value: 3210h size: 16-bit bit description 31:4 reserved 3:0 gbe lan pin (lip) ? r/w. indicates which pin the internal gbe lan controller drives as its interrupt 0h = no interrupt 1h = inta# (default) 2h = intb# 3h = intc# 4h = intd# 5h-fh = reserved bit description 15 reserved 14:12 interrupt d pin route (idr) ? r/w. indicates which physical pin on the intel ich is connected to the intd# pin re ported for device 31 functions. 0h = pirqa# 1h = pirqb# 2h = pirqc# 3h = pirqd# (default) 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# 11 reserved 10:8 interrupt c pin route (icr) ? r/w. indicates which ph ysical pin on the ich is connected to the intc# pin repo rted for device 31 functions. 0h = pirqa# 1h = pirqb# 2h = pirqc# (default) 3h = pirqd# 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# 7 reserved http://www..net/ datasheet pdf - http://www..net/ datasheet 335 chipset configuration registers 10.1.62 d30ir?device 30 in terrupt route register offset address: 3142?3143h attribute: ro default value: 0000h size: 16-bit 6:4 interrupt b pin route (ibr) ? r/w. indicates which ph ysical pin on the ich is connected to the intb# pin repo rted for device 31 functions. 0h = pirqa# 1h = pirqb# (default) 2h = pirqc# 3h = pirqd# 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# 3 reserved 2:0 interrupt a pin route (iar) ? r/w. indicates which ph ysical pin on the ich is connected to the inta# pin repo rted for device 31 functions. 0h = pirqa# (default) 1h = pirqb# 2h = pirqc# 3h = pirqd# 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# bit description bit description 15:0 reserved. no interrupts generate d from device 30. http://www..net/ datasheet pdf - http://www..net/ chipset configuration registers 336 datasheet 10.1.63 d29ir?device 29 in terrupt route register offset address: 3144?3145h attribute: r/w default value: 3210h size: 16-bit bit description 15 reserved 14:12 interrupt d pin route (idr) ? r/w. indicates which ph ysical pin on the intel ich is connected to the intd# pin re ported for device 29 functions. 0h = pirqa# 1h = pirqb# 2h = pirqc# 3h = pirqd# (default) 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# 11 reserved 10:8 interrupt c pin route (icr) ? r/w. indicates which ph ysical pin on the ich is connected to the intc# pin repo rted for device 29 functions. 0h = pirqa# 1h = pirqb# 2h = pirqc# (default) 3h = pirqd# 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# 7 reserved 6:4 interrupt b pin route (ibr) ? r/w. indicates which ph ysical pin on the ich is connected to the intb# pin repo rted for device 29 functions. 0h = pirqa# 1h = pirqb# (default) 2h = pirqc# 3h = pirqd# 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# 3 reserved 2:0 interrupt a pin route (iar) ? r/w. indicates which ph ysical pin on the ich is connected to the inta# pin repo rted for device 29 functions. 0h = pirqa# (default) 1h = pirqb# 2h = pirqc# 3h = pirqd# 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# http://www..net/ datasheet pdf - http://www..net/ datasheet 337 chipset configuration registers 10.1.64 d28ir?device 28 in terrupt route register offset address: 3146?3147h attribute: r/w default value: 3210h size: 16-bit bit description 15 reserved 14:12 interrupt d pin route (idr) ? r/w. indicates which ph ysical pin on the intel ich is connected to the intd# pin re ported for device 28 functions. 0h = pirqa# 1h = pirqb# 2h = pirqc# 3h = pirqd# (default) 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# 11 reserved 10:8 interrupt c pin route (icr) ? r/w. indicates which ph ysical pin on the ich is connected to the intc# pin repo rted for device 28 functions. 0h = pirqa# 1h = pirqb# 2h = pirqc# (default) 3h = pirqd# 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# 7 reserved 6:4 interrupt b pin route (ibr) ? r/w. indicates which ph ysical pin on the ich is connected to the intb# pin repo rted for device 28 functions. 0h = pirqa# 1h = pirqb# (default) 2h = pirqc# 3h = pirqd# 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# 3 reserved 2:0 interrupt a pin route (iar) ? r/w. indicates which ph ysical pin on the ich is connected to the inta# pin repo rted for device 28 functions. 0h = pirqa# (default) 1h = pirqb# 2h = pirqc# 3h = pirqd# 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# http://www..net/ datasheet pdf - http://www..net/ chipset configuration registers 338 datasheet 10.1.65 d27ir?device 27 in terrupt route register offset address: 3148?3149h attribute: r/w default value: 3210h size: 16-bit bit description 15 reserved 14:12 interrupt d pin route (idr) ? r/w. indicates which ph ysical pin on the intel ich is connected to the intd# pin re ported for device 27 functions. 0h = pirqa# 1h = pirqb# 2h = pirqc# 3h = pirqd# (default) 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# 11 reserved 10:8 interrupt c pin route (icr) ? r/w. indicates which ph ysical pin on the ich is connected to the intc# pin repo rted for device 27 functions. 0h = pirqa# 1h = pirqb# 2h = pirqc# (default) 3h = pirqd# 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# 7 reserved 6:4 interrupt b pin route (ibr) ? r/w. indicates which ph ysical pin on the ich is connected to the intb# pin repo rted for device 27 functions. 0h = pirqa# 1h = pirqb# (default) 2h = pirqc# 3h = pirqd# 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# 3 reserved 2:0 interrupt a pin route (iar) ? r/w. indicates which ph ysical pin on the ich is connected to the inta# pin repo rted for device 27 functions. 0h = pirqa# (default) 1h = pirqb# 2h = pirqc# 3h = pirqd# 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# http://www..net/ datasheet pdf - http://www..net/ datasheet 339 chipset configuration registers 10.1.66 d26ir?device 26 in terrupt route register offset address: 314c?314dh attribute: r/w default value: 3210h size: 16-bit bit description 15 reserved 14:12 interrupt d pin route (idr) ? r/w. indicates which phys ical pin on the ich is connected to the intd# pin repo rted for device 26 functions: 0h = pirqa# 1h = pirqb# 2h = pirqc# 3h = pirqd# (default) 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# 11 reserved 10:8 interrupt c pin route (icr) ? r/w. indicates which ph ysical pin on the ich is connected to the intc# pin repo rted for device 26 functions. 0h = pirqa# 1h = pirqb# 2h = pirqc# (default) 3h = pirqd# 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# 7 reserved 6:4 interrupt b pin route (ibr) ? r/w. indicates which ph ysical pin on the ich is connected to the intb# pin repo rted for device 26 functions. 0h = pirqa# 1h = pirqb# (default) 2h = pirqc# 3h = pirqd# 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# 3 reserved 2:0 interrupt a pin route (iar) ? r/w. indicates which ph ysical pin on the ich is connected to the inta# pin repo rted for device 26 functions. 0h = pirqa# (default) 1h = pirqb# 2h = pirqc# 3h = pirqd# 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# http://www..net/ datasheet pdf - http://www..net/ chipset configuration registers 340 datasheet 10.1.67 d25ir?device 25 in terrupt route register offset address: 3150?3151h attribute: r/w default value: 3210h size: 16-bit bit description 15 reserved 14:12 interrupt d pin route (idr): ? r/w. indicates which ph ysical pin on the ich is connected to the intd# pin repo rted for device 25 functions: 0h = pirqa# 1h = pirqb# 2h = pirqc# 3h = pirqd# (default) 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# 11 reserved 10:8 interrupt c pin route (icr) ? r/w. indicates which ph ysical pin on the ich is connected to the intc# pin repo rted for device 25 functions. 0h = pirqa# 1h = pirqb# 2h = pirqc# (default) 3h = pirqd# 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# 7 reserved 6:4 interrupt b pin route (ibr) ? r/w. indicates which ph ysical pin on the ich is connected to the intb# pin repo rted for device 25 functions. 0h = pirqa# 1h = pirqb# (default) 2h = pirqc# 3h = pirqd# 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# 3 reserved 2:0 interrupt a pin route (iar) ? r/w. indicates which ph ysical pin on the ich is connected to the inta# pin repo rted for device 25 functions. 0h = pirqa# (default) 1h = pirqb# 2h = pirqc# 3h = pirqd# 4h = pirqe# 5h = pirqf# 6h = pirqg# 7h = pirqh# http://www..net/ datasheet pdf - http://www..net/ datasheet 341 chipset configuration registers 10.1.68 oic?other interrupt contro l register (corporate only) offset address: 31fe?31ffh attribute: r/w default value: 0000h size: 16-bit note: fec10000h ? fec3ffffh is allocated to pcie when i/oxapic enable (pae) bit is set. 10.1.69 oic?other interrupt cont rol register (c onsumer only) offset address: 31ff?31ffh attribute: r/w default value: 00h size: 8-bit bit description 15:10 reserved 9 coprocessor error enable (cen) ? r/w. 0 = ferr# will not generate irq13 nor ignne#. 1 = if ferr# is low, the intel ich10 generate s irq13 internally and holds it until an i/o port f0h write. it will also drive ignne# active. 8 apic enable (aen) ? r/w. 0 = the internal ioxapic is disabled. 1 = enables the internal ioxa pic and its address decode. note: sw should read this register after modi fying apic enable bi t prior to access to the ioxapic address range. 7:0 apic range select (asel) ? r/w.these bits define a ddress bits 19:12 for the ioxapic range. the default value of 00h enables compatibility with prior ich products as an initial value. this value must not be changed unless the ioxapic enable bit is cleared. bit description 7:4 apic range select (asel) ? r/w.these bits define a ddress bits 15:12 for the ioxapic range. the default value of 0h enab les compatibility with prior ich products as an initial value. this value must not be changed unless the ioxapic enable bit is cleared. 3:2 reserved 1 coprocessor error enable (cen) ? r/w. 0 = ferr# will not generate irq13 nor ignne#. 1 = if ferr# is low, the intel ? ich10 generates irq13 internally and holds it until an i/o port f0h write. it will also drive ignne# active. 0 apic enable (aen) ? r/w. 0 = the internal ioxapic is disabled. 1 = enables the internal ioxa pic and its a ddress decode. note: sw should read this register after modify ing apic enable bit prior to access to the ioxapic address range. http://www..net/ datasheet pdf - http://www..net/ chipset configuration registers 342 datasheet 10.1.70 sbemc3?scheduled brea k event c3 exit latency offset address: 3300?3303h attribute: r/w default value: 00000000h size: 32-bit 10.1.71 sbemc4?scheduled brea k event c4 exit latency offset address: 3304?3307h attribute: r/w default value: 00000000h size: 32-bit bit description 31:23 reserved. 22:16 present state c3 future state c3 exit latency (c3c3el) ? r/w. sets exit latency if presen t and future c-state is c3. 15 reserved. 14:8 present state c2 future state c3 exit latency (c2c3el) ? r/w. sets exit latency if present c-stat e is c2 and future c-state is c3. 7 reserved. 6:0 present state c0 future state c3 exit latency (c0c3el) ? r/w. sets exit latency if present c-stat e is c0 and future c-state is c3. bit description 31 reserved. 30:24 present state c4 future state c4 exit latency (c4c4el) ? r/w. sets exit latency if presen t and future c-state is c4. 22:16 present state c3 future state c4 exit latency (c3c4el) ? r/w. sets exit latency if present c-stat e is c3 and future c-state is c4. 15 reserved. 14:8 present state c2 future state c4 exit latency (c2c4el) ? r/w. sets exit latency if present c-stat e is c2 and future c-state is c4. 7 reserved. 6:0 present state c0 future state c4 exit latency (c0c4el) ? r/w. sets exit latency if present c-stat e is c0 and future c-state is c4. http://www..net/ datasheet pdf - http://www..net/ datasheet 343 chipset configuration registers 10.1.72 prsts?power and reset status (corporate only) offset address: 3310?3313h attribute: ro, r/wc default value: tbdh size: 32-bit bit description 31:16 reserved 15 power management watchdog timer- r/wc. this bit is set when the power management watchdog time r causes a global reset. 14:7 reserved 6 intel ? management engine watchdog timer status -r/wc. this bit is set when the intel ? management engine watchdog timer causes a global reset. 5 wake on lan override wake status (wol_ovr_wk_sts) ? r/wc. this bit gets set when all of the following conditions are met: ? integrated lan signals a power management event ? the system is not in s0 ? the ?wol enable override? bit is set in configuration space. bios can read this status bit to determine this wake source. software clears this bi t by writing a 1 to it. 4 reserved 3 me host power down (me_host_pwrdn) ? r/wc.this bit is set when the intel me generates a host re set with power down. 2 me host reset warm status (me_hrst_warm_sts) ? r/wc. this bit is set when the intel management engine genera tes a host reset without power cycling. software clears this bit by wr iting a 1 to this bit position. 1 me host reset cold status (me_hrst_cold_sts) ? r/wc. this bit is set when the intel management engine generates a ho st reset with power cycling. software clears this bit by writing a 1 to this bit position. 0 me wake status (me_wake_sts) ? r/wc. this bit is set when the intel management engine generates a non-maskable wake event, and is not affected by any other enable bit. when this bit is set, the host power management logic wakes to s0. http://www..net/ datasheet pdf - http://www..net/ chipset configuration registers 344 datasheet 10.1.73 rc?rtc configuration register offset address: 3400?3403h attribute: r/w, r/wlo default value: 00000000h size: 32-bit 10.1.74 hptc?high precision timer configuration register offset address: 3404?3407h attribute: r/w default value: 00000000h size: 32-bit bit description 31:5 reserved 4 upper 128 byte lock (ul) ? r/wlo. 0 = bytes not locked. 1 = bytes 38h-3fh in the upper 128-byte bank of rtc ram are locked and cannot be accessed. writes will be dr opped and reads will not re turn any ensured data. bit reset on system reset. 3 lower 128 byte lock (ll) ? r/wlo. 0 = bytes not locked. 1 = bytes 38h-3fh in the lower 128-byte bank of rtc ram are locked and cannot be accessed. writes will be dr opped and reads will not re turn any ensured data. bit reset on system reset. 2 upper 128 byte enable (ue) ? r/w. 0 = bytes locked. 1 = the upper 128-byte bank of rtc ram can be accessed. 1:0 reserved bit description 31:8 reserved 7 address enable (ae) ? r/w. 0 = address disabled. 1 = the intel ? ich10 will decode the high prec ision timer memory address range selected by bits 1:0 below. 6:2 reserved 1:0 address select (as) ? r/w. this 2-bit field selects 1 of 4 possible memory address ranges for the high precision time r functionality. the encodings are: 00 = fed0_0000h ? fed0_03ffh 01 = fed0_1000h ? fed0_13ffh 10 = fed0_2000h ? fed0_23ffh 11 = fed0_3000h ? fed0_33ffh http://www..net/ datasheet pdf - http://www..net/ datasheet 345 chipset configuration registers 10.1.75 gcs?general contro l and status register offset address: 3410?3413h attribute: r/w, r/wlo default value: 00000yy0h (yy = xx0000x0b)size: 32-bit bit description 31:13 reserved. 12 function level reset capability structure select (flrcssel) ? r/w. 0 = function level reset (flr) will utilize the standard capability structure with unique capability id assigned by pcisig. 1 = vendor specific capability structure is selected for flr. 11:10 boot bios straps (bbs) ? r/w. this field determines the destination of accesses to the bios memory range. the default values for these bits represent the strap values of gnt0# (bit 11) at the rising ed ge of pwrok and spi_cs1#(bit 10) at the rising edge of clpwrok. when pci is selected, the top 16 mb of memory below 4 gb (ff00_0000h to ffff_ffffh) is accepted by the primary side of the pci p2p bridge and forwarded to the pci bus. this allows systems with co rrupted or unprogrammed flash to boot from a pci device. the pci-to-pci bridge memory space enable bit does not need to be set (nor any other bits) in order for these cycles to go to pc i. note that bios decode range bits and the other bios protection bits have no e ffect when pci is selected. this functionality is intend ed for debug/testing only. when spi or lpc is selected, the range that is decoded is further qualified by other configuration bits described in the respective sections. the value in this field can be overwritten by software as long as the bios interface lock-down (bit 0) is not set. note: booting to pci is intended for debug/ testing only. boot bios destination select to lpc/pci by functional strap or via boot bios destination bit will not affect spi accesses initia ted by intel management en gine or integrated gbe lan. 9 server error reporting mode (serm) ? r/w. 0 = the intel ? ich10 is the final target of all er rors. the (g)mch sends a messages to the ich for the purpose of generating nmi. 1 = the (g)mch is the final target of all errors from pci express* and dmi. in this mode, if the ich10 detects a fatal, non-fatal, or correc table error on dmi or its downstream ports, it sends a message to the (g)mch. if the ich10 receives an err_* message from the downstream po rt, it sends that message to the (g)mch. 8:7 reserved 6 ferr# mux enable (fme) ? r/w. this bit enables ferr# to be a processor break event indication. 0 = disabled. 1 = the ich10 examines ferr# during a c2, c3, or c4 state as a break event. see chapter 5.13.5 for a function al description. bits 11:10 description 0xb spi 10b pci 11b lpc http://www..net/ datasheet pdf - http://www..net/ chipset configuration registers 346 datasheet 5 no reboot (nr) ? r/w. this bit is set when the ?no reboot? strap (spkr pin on ich10) is sampled high on pwrok. this bit may be set or cleared by software if the strap is sampled low but may not override the strap when it indicates ?no reboot?. 0 = system will reboot upon the second timeout of the tco timer. 1 = the tco timer will count down and gene rate the smi# on the first timeout, but will not reboot on the second timeout. 4 alternate access mode enable (ame) ? r/w. 0 = disabled. 1 = alternate access read only registers ca n be written, and writ e only registers can be read. before entering a low power st ate, several register s from powered down parts may need to be saved. in the majori ty of cases, this is not an issue, as registers have read and write paths. ho wever, several of the isa compatible registers are either read only or write only. to get data out of write-only registers, and to restore data into read-only registers, the ich implements an alternate access mode. for a list of these registers see section 5.13.9 . 3 shutdown policy select (sps) ? r/w. when cleared (d efault), the ich10 will drive init# in response to the shutdown vendor defined message (vdm). when set to 1, ich10 will treat the shutdown vdm similar to receiving a cf9h i/o write with data value06h, and will drive pltrst# active. 2 reserved page route (rpr) ? r/w. determines where to send the reserved page registers. these addresses are sent to pci or lpc for the purpose of generating post codes. the i/o addresses modified by this field are: 80h, 84h, 85h, 86h, 88h, 8ch, 8dh, and 8eh. 0 = writes will be forwarded to lpc, shad owed within the ich, and reads will be returned from the internal shadow 1 = writes will be forwarded to pci, shad owed within the ich, and reads will be returned from the internal shadow. note, if some writes are done to lpc/pci to these i/o ranges, and then this bit is flipped, such that writes wi ll now go to the other interface , the reads will not return what was last written. shadowing is performed on each interface. the aliases for these register s, at 90h, 94h, 95h, 96h, 98h, 9ch, 9dh, and 9eh, are always decoded to lpc. 1 reserved 0 bios interface lock-down (bild) ? r/wlo. 0 = disabled. 1 = prevents buc.ts (offset 3414, bit 0) and gcs.bbs (offset 3410h, bits 11:10) from being changed. this bit can on ly be written from 0 to 1 once. bit description http://www..net/ datasheet pdf - http://www..net/ datasheet 347 chipset configuration registers 10.1.76 buc?backed up control register offset address: 3414?3414h attribute: r/w default value: 0000000xb size: 8-bit all bits in this register are in the rtc well and only cleared by rtcrst# bit description 7:6 reserved 5 lan disable ? r/w. 0 = lan is enabled 1 = lan is disabled. this bit is locked by the function disabl e sus well lockdown register. once locked this bit can not be changed by software. 4 daylight savings override (sdo) ? r/w. 0 = daylight savings is enabled. 1 = the dse bit in rtc register b is set to read-only with a value of 0 to disable daylight savings. 3 reserved 2 cpu bist enable (cbe) ? r/w. this bit is in the resume well and is reset by rsmrst#, but not pltr st# nor cf9h writes. 0 = disabled. 1 = the init# signals will be driven ac tive when cpurst# is active. init# and init3_3v# will go inactive with the same timings as the other processor interface signals (hold time after cpurst# inactive). 1 reserved 0 top swap (ts) ? r/w. 0 = intel ? ich10 will not invert a16. 1 = ich10 will invert a16 for cycles going to the bios space (but not the feature space) in the fwh. if ich is strapped for top-swap (gnt3# is lo w at rising edge of pwrok), then this bit cannot be cleared by software. the strap jumper should be removed and the system rebooted. http://www..net/ datasheet pdf - http://www..net/ chipset configuration registers 348 datasheet 10.1.77 fd?function disable register offset address: 3418?341bh attribute: r/w default value: see bit description size: 32-bit the uhci functions must be disabled from highest function number to lowest within each pci device (device 29 or device 26). for example, if only two uhcis are wanted on device 29, software must disable uhci #3 (ud3 bit set). when disabling uhcis, the ehci structural parameters registers must be updated with coherent information in ?number of companion controllers? and ?n_ports? fields. when disabling a function, only the configuration space is disabled. software must ensure that all functionality within a controller that is not desired (such as memory spaces, i/o spaces, and dma engines) is disabled prior to disabling the function. when a function is disabled, software must not attempt to re-enable it. a disabled function can only be re-enabled by a platform reset. bit description 31:26 reserved 25 serial ata disable 2 (sad2) ? r/w. default is 0. 0 = the sata controller #2 (d31:f5) is enabled. 1 = the sata controller #2 (d31:f5) is disabled. 24 thermal throttle disable (ttd) ? r/w. default is 0. 0 = thermal throttle is enabled. 1 = thermal throttle is disabled. 23:22 reserved 21 pci express* 6 disable (pe6d) ? r/w. default is 0. when disabled, the link for this port is put into the ?link down? state. 0 = pci express* po rt #6 is enabled. 1 = pci express port #6 is disabled. 20 pci express 5 disable (pe5d) ? r/w. default is 0. when disabled, the link for this port is put into the link down state. 0 = pci express port #5 is enabled. 1 = pci express port #5 is disabled. 19 pci express 4 disable (pe4d) ? r/w. default is 0. when disabled, the link for this port is put into the ?link down? state. 0 = pci express port #4 is enabled. 1 = pci express port #4 is disabled. note: this bit must be set when po rt 1 is configured as a x4. 18 pci express 3 disable (pe3d) ? r/w. default is 0. when disabled, the link for this port is put into the link down state. 0 = pci express port #3 is enabled. 1 = pci express port #3 is disabled. note: this bit must be set when po rt 1 is configured as a x4. 17 pci express 2 disable (pe2d) ? r/w. default is 0. when disabled, the link for this port is put into the link down state. 0 = pci express port #2 is enabled. 1 = pci express port #2 is disabled. note: this bit must be set when port 1 is configured as a x4 or a x2. http://www..net/ datasheet pdf - http://www..net/ datasheet 349 chipset configuration registers 16 pci express 1 disable (pe1d) ? r/w. default is 0. when disabled, the link for this port is put into the link down state. 0 = pci express port #1 is enabled. 1 = pci express port #1 is disabled. 15 ehci #1 disable (ehci1d) ? r/w. default is 0. 0 = the ehci #1 is enabled. 1 = the ehci #1 is disabled. 14 lpc bridge disable (lbd) ? r/w. default is 0. 0 = the lpc bridge is enabled. 1 = the lpc bridge is disabl ed. unlike the other disables in this register, the following additional spaces will no longer be decoded by the lpc bridge: ? memory cycles below 16 mb (1000000h) ? i/o cycles below 64 kb (10000h) ? the internal i/oxapic at fec0_0000 to fecf_ffff memory cycles in the lpc bios range below 4 gb will still be de coded when this bit is set, but the aliases at the top of 1 mb (the e and f segment) no longer will be decoded. 13 ehci #2 disable (ehci2d) ? r/w. default is 0. 0 = the ehci #2 is enabled. 1 = the ehci #2 is disabled. note: when this bit is set, the uhci #5 function is not available and the uhci #4 must be disabled by settin g bit 11 in this register. 12 uhci #5 disable (u5d) ? r/w. default is 0 0 = the uhci #5 is enabled. 1 = the uhci #5 is disabled. when the ehci #2 device disable (ehci2d) is set, this bit is a don?t care 11 uhci #4 disable (u4d) ? r/w. default is 0. 0 = the 4th uhci (ports 6 and 7) is enabled. 1 = the 4th uhci (ports 6 and 7) is disabled. note that uhci #4 must be disabled when ehci #2 is disabled with bit 13 in this register. 10 uhci #3 disable (u3d) ? r/w. default is 0. 0 = the 3rd uhci (ports 4 and 5) is enabled. 1 = the 3rd uhci (ports 4 and 5) is disabled. 9 uhci #2 disable (u2d) ? r/w. default is 0. 0 = the 2nd uhci (ports 2 and 3) is enabled. 1 = the 2nd uhci (ports 2 and 3) is disabled. 8 uhci #1 disable (u1d) ? r/w. default is 0. 0 = the 1st uhci (ports 0 and 1) is enabled. 1 = the 1st uhci (ports 0 and 1) is disabled. 7 uhci #6 disable (u6d) ? r/w. default is 0. 0 = the 6th uhci (ports 10 and 11) is enabled. 1 = the 6th uhci (ports 10 and 11) is disabled. 6:5 (corporate only) usb test devices #1 and #2 ? r/w . default is 0. bios must set these bits to 11b. note: these bits only apply to ich10 corp orate a0, a1, and b0 samples and are reserved for ich10 corporate production units. bit description http://www..net/ datasheet pdf - http://www..net/ chipset configuration registers 350 datasheet 10.1.78 cg?clock gating offset address: 341c?341fh attribute: r/w default value: 00000000h size: 32-bit 6:5 (consumer only) reserved 4 intel ? high definition audio disable (hdad) ? r/w. default is 0. 0 = the intel high definition audio controller is enabled. 1 = the intel high definition audio controller is disabled and its pci configuration space is not accessible. 3 smbus disable (sd) ? r/w. default is 0. 0 = the smbus controller is enabled. 1 = the smbus controller is disabled. in ic h5 and previous, this also disabled the i/ o space. in ich10, it only di sables the configuration space. 2 serial ata disable 1 (sad1) ? r/w. default is 0. 0 = the sata controller #1 (d31:f2) is enabled. 1 = the sata controller #1 (d31:f2) is disabled. 1reserved 0 bios must set this bit to 1b. bit description bit description 31 legacy (lpc) dynamic clock gate enable ? r/w. 0 = legacy dynamic clock gating is disabled 1 = legacy dynamic clock gating is enabled 30 reserved 29:28 usb uhci dynamic clock gate enable ? r/w. 0 = usb uhci dynamic clock gating is disabled 1 = usb uhci dynamic clock gating is enabled 0 = reserved 1 = reserved 27 sata port 3 dynamic clock gate enable ? r/w. 0 = sata port 3 dynamic clock gating is disabled 1 = sata port 3 dynamic clock gating is enabled 26 sata port 2 dynamic clock gate enable ? r/w. 0 = sata port 2 dynamic clock gating is disabled 1 = sata port 2 dynamic clock gating is enabled 25 sata port 1 dynamic clock gate enable ? r/w. 0 = sata port 1 dynamic clock gating is disabled 1 = sata port 1 dynamic clock gating is enabled 24 sata port 0 dynamic clock gate enable ? r/w. 0 = sata port 0 dynamic clock gating is disabled 1 = sata port 0 dynamic clock gating is enabled http://www..net/ datasheet pdf - http://www..net/ datasheet 351 chipset configuration registers 23 lan static clock gating enable (lanscge) ? r/w. 0 = lan static clock gating is disabled 1 = lan static clock gating is enabled when the lan disable bit is set in the backed up control rtc register. 22 high definition audio dynamic clock gate enable ? r/w. 0 = high definition audio dynamic clock gating is disabled 1 = high definition audio dynamic clock gating is enabled 21 high definition audio static clock gate enable ? r/w. 0 = high definition audio static clock gating is disabled 1 = high definition audio static clock gating is enabled 20 usb ehci static clock gate enable ? r/w. 0 = usb ehci static cl ock gating is disabled 1 = usb ehci static clock gating is enabled 19 usb ehci dynamic clock gate enable ? r/w. 0 = usb ehci dynamic clock gating is disabled 1 = usb ehci dynamic clock gating is enabled 18 sata port 5 dynamic clock gate enable ? r/w. 0 = sata port 5 dynamic clock gating is disabled 1 = sata port 5 dynamic clock gating is enabled 17 sata port 4 dynamic clock gate enable ? r/w. 0 = sata port 4 dynamic clock gating is disabled 1 = sata port 4 dynamic clock gating is enabled 16 pci dynamic gate enable ? r/w. 0 = pci dynamic gating is disabled 1 = pci dynamic gating is enabled 15:6 reserved 5 smbus clock gating enable (smbcgen) ? r/w. 0 = smbus clock gating is disabled. 1 = smbus clock gating is enabled. 4 pci express* rx clock ga ting enable (prxcgen) ? r/w. 0 = afe rx clock gating is disabled 1 = afe rx clock gating is enabled when ever all pcie ports rx are in squelch 3 dmi and pci express* rx dynamic clock gate enable ? r/w. 0 = dmi and pci express root port rx dynamic clock gating is disabled 1 = dmi and pci express root port rx dynamic clock gating is enabled 2 pci express tx dynami c clock gate enable ? r/w. 0 = pci express root port tx dy namic clock gating is disabled 1 = pci express root port tx dy namic clock gating is enabled 1 dmi tx dynamic clock gate enable ? r/w. 0 = dmi tx dynamic clock gating is disabled 1 = dmi tx dynamic clock gating is enabled 0 pci express root port st atic clock gate enable ? r/w. 0 = pci express root port stat ic clock gating is disabled 1 = pci express root port stat ic clock gating is enabled bit description http://www..net/ datasheet pdf - http://www..net/ chipset configuration registers 352 datasheet 10.1.79 fdsw?function disable sus well offset address: 3420h attribute: r/w default value: 00h size: 8-bit 10.1.80 cir8?chipset init ialization register 8 offset address: 3430-3433h attribute: r/w default value: 00000000h size: 32-bit 10.1.81 cir9?chipset init ialization register 9 offset address: 350ch?350fh attribute: r/w default value: 00000000h size: 32-bit 10.1.82 ppo?port power off offset address: 3524?3525h attribute: r/w default value: 0000h size: 16-bit bit description 7 function disable sus well lockdown (fdswl) ? r/w 0 = fdsw registers are not locked down 1 = fdsw registers are locked down 6:0 reserved bit description 7:2 reserved 1:0 cir8 field 1 ? r/w. bios must program this field to 10b. bit description 31:28 reserved 27:26 cir9 field 1 ? r/w. bios must program this field to 10b. 25:0 reserved bit description 15:12 reserved 11:0 usb port power off ? r/w 1 = the corresponding ehci and uhci ports are electrically disconnected in this mode. warning: the platform must ensu re that the powered off ports are not routed to any internal usb header or external usb connector. the ich provides pull-down termination resistors. this register can not be wr itten when the usb per-port registers write enable bit (uprwc register, pmbase + 3c, bit 1) is 0. http://www..net/ datasheet pdf - http://www..net/ datasheet 353 chipset configuration registers 10.1.83 cir10?chipset init ialization register 10 offset address: 352c?352fh attribute: r/w default value: 0008c008h size: 32-bit 10.1.84 map?remap control register offset address: 35f0?35f3h attribute: r/wo default value: 00000000h size: 32-bit bit description 32:18 reserved 17:16 cir10 field 1 ? r/w. bios must program this field to 11b. 15:0 reserved bit description 31:01 reserved 0 uhci controller # 6 remap ? r/wo 1 = uhci controller #6 is ma pped to device 29 function 3 0 = uhci controller #6 is ma pped to device 26 function 2 note: when this bit is set, sw shou ld reprogram the hcsparams register ( section 17.2.1.3 ) to reflect the correct value fo r n_cc (bits 15:12) and n_ports (bits 3:0) in each ehci controller. http://www..net/ datasheet pdf - http://www..net/ chipset configuration registers 354 datasheet http://www..net/ datasheet pdf - http://www..net/ datasheet 355 pci-to-pci bridge registers (d30:f0) 11 pci-to-pci bridge registers (d30:f0) the ich10 pci bridge resides in pci device 30, function 0 on bus #0. this implements the buffering and control logic between pci and the backbone. the arbitration for the pci bus is handled by this pci device. 11.1 pci configuration registers (d30:f0) note: address locations that are not shown should be treated as reserved (see section 9.2 for details). . table 11-1. pci bridge regi ster address map (pci-pci ?d30:f0) (sheet 1 of 2) offset mnemonic register name default type 00h?01h vid vendor identification 8086h ro 02h?03h did device identification see register description ro 04h?05h pcicmd pci command 0000h r/w, ro 06h?07h psts pci status 0010h r/wc, ro 08h rid revision identification see register description ro 09h?0bh cc class code 060401h ro 0dh pmlt primary master latency timer 00h ro 0eh headtyp header type 01h ro 18h?1ah bnum bus number 000000h ro 1bh smlt secondary master latency timer 00h r/w 1ch?1dh iobase_limit i/o base and limit 0000h r/w, ro 1eh?1fh secsts secondary status 0280h r/wc, ro 20h?23h membase_limit memory base and limit 00000000h r/w 24h?27h pref_mem_base _limit prefetchable memory base and limit 00010001h r/w, ro 28h?2bh pmbu32 prefetchable memory upper 32 bits 00000000h r/w 2ch?2fh pmlu32 prefetchable memory limit upper 32 bits 00000000h r/w 34h capp capability list pointer 50h ro 3ch?3dh intr interrupt information 0000h r/w, ro 3eh?3fh bctrl bridge control 0000h r/wc, ro, r/w 40h?41h spdh secondary pci device hiding 0000h r/w, ro 44h?47h dtc delayed transaction control 00000000h r/w 48h?4bh bps bridge proprietary status 00000000h r/wc, ro http://www..net/ datasheet pdf - http://www..net/ pci-to-pci bridge registers (d30:f0) 356 datasheet 11.1.1 vid? vendor identificati on register (pci-pci?d30:f0) offset address: 00h?01h attribute: ro default value: 8086h size: 16 bits 11.1.2 did? device identificati on register (pci-pci?d30:f0) offset address: 02h?03h attribute: ro default value: see bit description size: 16 bits 4ch?4fh bpc bridge policy configuration 00001200h r/w ro 50?51h svcap subsystem vendor capability pointer 000dh ro 54h?57h svid subsystem vendor ids 00000000 r/wo table 11-1. pci bridge regi ster address map (pci-pci?d30:f0) (sheet 2 of 2) offset mnemonic register name default type bit description 15:0 vendor id ? ro. this is a 16-bit value assi gned to intel. intel vid = 8086h. bit description 15:0 device id ? ro.this is a 16-bit value assigned to the pci bridge. refer to the intel ? i/o controller hub (ich10) fa mily specification update for the value of the device id register. http://www..net/ datasheet pdf - http://www..net/ datasheet 357 pci-to-pci bridge registers (d30:f0) 11.1.3 pcicmd?pci command (pci-pci?d30:f0) offset address: 04h ? 05h attribute: r/w, ro default value: 0000h size: 16 bits 11.1.4 psts?pci status register (pci-pci?d30:f0) offset address: 06h ? 07h attribute: r/wc, ro default value: 0010h size: 16 bits note: for the writable bits, software must write a 1 to clear bits that are set. writing a 0 to the bit has no effect. bit description 15:11 reserved 10 interrupt disable (id) ? ro. hardwired to 0. the pci bridge has no interrupts to disable 9 fast back to back enable (fbe ) ? ro. hardwired to 0, per the pci express* base specification, revision 1.0a . 8 serr# enable (serr_en) ? r/w. 0 = disable. 1 = enable the ich10 to generate an nmi (o r smi# if nmi routed to smi#) when the d30:f0 sse bit (offset 06h, bit 14) is set. 7 wait cycle control (wcc) ? ro. hardwired to 0, per the pci express* base specification, revision 1.0a . 6 parity error response (per) ? r/w. 0 = the ich10 ignores parity errors on the pci bridge. 1 = the ich10 will set the sse bit (d30:f0, o ffset 06h, bit 14) when parity errors are detected on the pci bridge. 5 vga palette snoop (vps) ? ro . hardwired to 0, per the pci express* base specification, revision 1.0a . 4 memory write and invalidate enable (mwe) ? ro. hardwired to 0, per the pci express* base specification, revision 1.0a 3 special cycle enable (sce) ? ro. hardwired to 0, per the pci express* base specification, revision 1.0a and the pci- to-pci bridge specification. 2 bus master enable (bme) ? r/w. 0 = disable 1 = enable. allows the pci-to-pci br idge to accept cycles from pci. 1 memory space enable (mse) ? r/w. controls the respon se as a target for memory cycles targeting pci. 0 = disable 1 = enable 0 i/o space enable (iose) ? r/w. controls the response as a target for i/o cycles targeting pci. 0 = disable 1 = enable http://www..net/ datasheet pdf - http://www..net/ pci-to-pci bridge registers (d30:f0) 358 datasheet bit description 15 detected parity error (dpe) ? r/wc. 0 = parity error not detected. 1 = indicates that the ich10 detected a parity error on the internal backbone. this bit gets set even if the parity error resp onse bit (d30:f0:04 bit 6) is not set. 14 signaled system error (sse) ? r/wc. several internal an d external sources of the bridge can cause serr#. the first class of errors is parity e rrors related to the backbone. the pci bridge captures generic da ta parity errors (errors it finds on the backbone) as well as errors returned on backbone cycles wher e the bridge was the master. if either of these two conditions is met, and the primary side of the bridge is enabled for parity error response, serr# will be captured as shown below. as with the backbone, the pci bus captures the same sets of e rrors. the pci bridge captures generic data parity erro rs (errors it finds on pci) as well as errors returned on pci cycles where the bridge was the master. if either of these two conditions is met, and the secondary side of the bridge is enab led for parity error response, serr# will be captured as shown below. the final class of errors is system bus errors. there are three status bits associated with system bus errors, each with a corresponding enable. the diagram capturing this is shown below. after checking for the three above classes of errors, an serr# is generated, and psts.sse logs the generation of serr#, if cmd.see (d30:f0:04, bit 8) is set, as shown below. 13 received master abort (rma) ? r/wc. 0 = no master abort received. 1 = set when the bridge receives a ma ster abort status from the backbone. http://www..net/ datasheet pdf - http://www..net/ datasheet 359 pci-to-pci bridge registers (d30:f0) 11.1.5 rid?revision identificati on register (pci-pci?d30:f0) offset address: 08h attribute: ro default value: see bit description size: 8 bits 11.1.6 cc?class code register (pci-pci?d30:f0) offset address: 09h-0bh attribute: ro default value: 060401h size: 24 bits 12 received target abort (rta) ? r/wc. 0 = no target abort received. 1 = set when the bridge receives a ta rget abort status from the backbone. 11 signaled target abort (sta) ? r/wc. 0 = no signaled target abort 1 = set when the bridge generates a completion packet with target abort status on the backbone. 10:9 reserved. 8 data parity error detected (dpd) ? r/wc. 0 = data parity error not detected. 1 = set when the bridge receives a comp letion packet from the backbone from a previous request, an d detects a parity error, and cm d.pere is set (d30:f0:04 bit 6). 7:5 reserved. 4 capabilities list (clist) ? ro. hardwired to 1. capability list exist on the pci bridge. 3 interrupt status (is) ? ro. hardwired to 0. the pci bridge does not generate interrupts. 2:0 reserved bit description bit description 7:0 revision id ? ro. refer to the intel ? i/o controller hub (ich10) family specification update for the value of the revision id register bit description 23:16 base class code (bcc) ? ro. hardwired to 06h. indicates this is a bridge device. 15:8 sub class code (scc) ? ro. hardwired to 04h. indicates th is device is a pci-to-pci bridge. 7:0 programming interface (pi) ? ro. hardwired to 01h. indi cates the bridge is subtractive decode http://www..net/ datasheet pdf - http://www..net/ pci-to-pci bridge registers (d30:f0) 360 datasheet 11.1.7 pmlt?primary master latency timer register (pci-pci?d30:f0) offset address: 0dh attribute: ro default value: 00h size: 8 bits 11.1.8 headtyp?header type register (pci-pci?d30:f0) offset address: 0eh attribute: ro default value: 01h size: 8 bits 11.1.9 bnum?bus number re gister (pci-pci?d30:f0) offset address: 18h-1ah attribute: r/w default value: 000000h size: 24 bits bit description 7:3 master latency timer count (mltc) ? ro. reserved per the pci express* base specification, revision 1.0a . 2:0 reserved bit description 7 multi-function device (mfd) ? ro. a 0 indicates a single function device 6:0 header type (htype) ? ro. this 7-bit field identifi es the header layout of the configuration space, which is a pci-to-pci bridge in this case. bit description 23:16 subordinate bus number (sbbn) ? r/w. this field indicates the highest pci bus number below the bridge. 15:8 secondary bus number (scbn) ? r/w. this field indicates the bus number of pci. 7:0 primary bus number (pbn) ? r/w. this field is default to 00h. in a multiple-ich system, programmable pbn allows an ic h to be located on any bus. system configuration software is responsible for in itializing these registers to appropriate values. pbn is not used by hardwa re in determinin g its bus number. http://www..net/ datasheet pdf - http://www..net/ datasheet 361 pci-to-pci bridge registers (d30:f0) 11.1.10 smlt?secondary master latency timer register (pci-pci?d30:f0) offset address: 1bh attribute: r/w default value: 00h size: 8 bits this timer controls the amount of time the ich10 pci-to-pci bridge will burst data on its secondary interface. the counter starts counting down from the assertion of frame#. if the grant is removed, then the ex piration of this counter will result in the de-assertion of frame#. if the grant has not been removed, then the ich10 pci-to-pci bridge may continue ownership of the bus. 11.1.11 iobase_limit?i/o ba se and limit register (pci-pci?d30:f0) offset address: 1ch-1dh attribute: r/w, ro default value: 0000h size: 16 bits bit description 7:3 master latency timer count (mltc) ? r/w. this 5-bit field indi cates the number of pci clocks, in 8-clock increments, that the ich10 remains as master of the bus. 2:0 reserved bit description 15:12 i/o limit address limit bits [15:12] ? r/w. i/o base bits corresponding to address lines 15:12 for 4-kb alignment. bits 11: 0 are assumed to be padded to fffh. 11:8 i/o limit address capability (iolc) ? ro. this field indicates that the bridge does not support 32-bit i/o addressing. 7:4 i/o base address (ioba) ? r/w. i/o base bits corresponding to address lines 15:12 for 4-kb alignment. bi ts 11:0 are assumed to be padded to 000h. 3:0 i/o base address capability (iobc) ? ro. this field indicate s that the bridge does not support 32-bit i/o addressing. http://www..net/ datasheet pdf - http://www..net/ pci-to-pci bridge registers (d30:f0) 362 datasheet 11.1.12 secsts?secondary status register (pci-pci?d30:f0) offset address: 1eh ? 1fh attribute: r/wc, ro default value: 0280h size: 16 bits note: for the writable bits, software must write a 1 to clear bits that are set. writing a 0 to the bit has no effect. bit description 15 detected parity error (dpe) ? r/wc. 0 = parity error not detected. 1 = intel ? ich10 pci bridge detected an address or data parity error on the pci bus 14 received system error ( rse) ? r/wc. 0 = serr# assertion not received 1 = serr# assertion is received on pci. 13 received master abort (rma) ? r/wc. 0 = no master abort. 1 = this bit is set whenever th e bridge is acting as an in itiator on the pci bus and the cycle is master-aborted. for (g)mch/ich10 interface packets that have completion required, this must also ca use a target abort to be re turned and sets psts.sta. (d30:f0:06 bit 11) 12 received target abort (rta) ? r/wc. 0 = no target abort. 1 = this bit is set whenever the bridge is acting as an initiator on pci and a cycle is target-aborted on pci. for (g)mch/ich10 interface packets that have completion required, this event must also cause a target abort to be returned, and sets psts.sta. (d30:f0:06 bit 11). 11 signaled target abort (sta) ? r/wc. 0 = no target abort. 1 = this bit is set when the br idge is acting as a target on the pci bus and signals a target abort. 10:9 devsel# timing (devt) ? ro. 01h = medium decode timing. 8 data parity error detected (dpd) ? r/wc. 0 = conditions de scribed below not met. 1 = the ich10 sets this bit when all of the following three conditions are met: ? the bridge is the initiator on pci. ? perr# is detected asserted or a parity error is detected internally ? bctrl.pere (d30:f0:3e bit 0) is set. 7 fast back to back capable (fbc) ? ro. hardwi red to 1 to indicate that the pci to pci target logic is capable of rece iving fast back-to-back cycles. 6 reserved 5 66 mhz capable (66mhz_cap) ? ro. hardwire d to 0. this bridge is 33 mhz capable only. 4:0 reserved http://www..net/ datasheet pdf - http://www..net/ datasheet 363 pci-to-pci bridge registers (d30:f0) 11.1.13 membase_limit?memory base and limit register (pci-pci?d30:f0) offset address: 20h?23h attribute: r/w default value: 00000000h size: 32 bits this register defines the base and limit, aligned to a 1-mb boundary, of the non- prefetchable memory area of the bridge. a ccesses that are within the ranges specified in this register will be sent to pci if cmd. mse is set. accesses from pci that are outside the ranges specified will be accepted by the bridge if cmd.bme is set. 11.1.14 pref_mem_base_limit?prefetchable memory base and limit register (pci-pci?d30:f0) offset address: 24h?27h attribute: r/w, ro default value: 00010001h size: 32-bit defines the base and limit, aligned to a 1- mb boundary, of the prefetchable memory area of the bridge. accesses that are within th e ranges specified in this register will be sent to pci if cmd.mse is set. accesses from pci that are outside the ranges specified will be accepted by the bridge if cmd.bme is set. bit description 31:20 memory limit (ml) ? r/w. these bits are compared with bits 31:20 of the incoming address to determine the upper 1-mb alig ned value (exclusive) of the range. the incoming address must be less than this value. 19:16 reserved 15:4 memory base (mb) ? r/w. these bits are compared with bits 31:20 of the incoming address to determine the lower 1-mb alig ned value (inclusive) of the range. the incoming address must be greate r than or equal to this value. 3:0 reserved bit description 31:20 prefetchable memory limit (pml) ? r/w. these bits are compared with bits 31:20 of the incoming address to determine the u pper 1-mb aligned value (exclusive) of the range. the incoming address mu st be less than this value. 19:16 64-bit indicator (i64l) ? ro. indicates support for 64-bit addressing. 15:4 prefetchable memory base (pmb) ? r/w. these bits are compared with bits 31:20 of the incoming address to determine the lo wer 1-mb aligned value (inclusive) of the range. the incoming address must be greater than or equal to this value. 3:0 64-bit indicator (i64b) ? ro. indicates support fo r 64-bit addressing. http://www..net/ datasheet pdf - http://www..net/ pci-to-pci bridge registers (d30:f0) 364 datasheet 11.1.15 pmbu32?prefetchable memory base upper 32 bits register (pci-pci?d30:f0) offset address: 28h?2bh attribute: r/w default value: 00000000h size: 32 bits 11.1.16 pmlu32?prefetchable memory limit upper 32 bits register (pci-pci?d30:f0) offset address: 2c?2fh attribute: r/w default value: 00000000h size: 32 bits 11.1.17 capp?capability list poin ter register (pci-pci?d30:f0) offset address: 34h attribute: ro default value: 50h size: 8 bits 11.1.18 intr?interrupt informat ion register (pci-pci?d30:f0) offset address: 3ch ? 3dh attribute: r/w, ro default value: 0000h size: 16 bits bit description 31:0 prefetchable memory base upper portion (pmbu) ? r/w. upper 32-bits of the prefetchable address base. bit description 31:0 prefetchable memory limit upper portion (pmlu) ? r/w. upper 32-bits of the prefetchable address limit. bit description 7:0 capabilities pointer (ptr) ? ro. this field indicates that the pointer for the first entry in the capabilities list is at 50h in configuration space. bit description 15:8 interrupt pin (ipin) ? ro. the pci bridge does not assert an interrupt. 7:0 interrupt line (iline) ? r/w. software written value to indicate which interrupt line (vector) the interrupt is conn ected to. no hardware action is taken on this register. since the bridge does not gene rate an interrupt, bios should program this value to ffh as per the pci bri dge specification. http://www..net/ datasheet pdf - http://www..net/ datasheet 365 pci-to-pci bridge registers (d30:f0) 11.1.19 bctrl?bridge control register (pci-pci?d30:f0) offset address: 3eh ? 3fh attribute: r/wc, ro, r/w default value: 0000h size: 16 bits bit description 15:12 reserved 11 discard timer serr# enable (dte ) ? r/w. this bit controls the generation of serr# on the primary interface in response to the dts bit being set: 0 = do not generate serr# on a secondary timer discard 1 = generate serr# in response to a secondary timer discard 10 discard timer status (dts) ? r/wc. this bit is set to 1 when the secondary discard timer (see the sdt bit below) expires for a delayed transaction in the hard state. 9 secondary discard timer (sdt) ? r/w. this bit sets the maximum number of pci clock cycles that the intel ? ich10 waits for an initiator on pci to repeat a delayed transaction request. the counter starts once the delayed transaction data is has been returned by the system and is in a buffer in the ich10 pci bridge. if the master has not repeated the transaction at least once before the counter expires, the ich10 pci bridge discards the transaction from its queue. 0 = the pci master timeout value is between 2 15 and 2 16 pci clocks 1 = the pci master timeout value is between 2 10 and 2 11 pci clocks 8 primary discard timer (pdt ) ? r/w. this bit is r/w for software compatibility only. 7 fast back to back enable (fbe) ? ro. hardwi red to 0. the pci logi c will not generate fast back-to-back cycles on the pci bus. 6 secondary bus reset (sbr) ? r/w. this bit controls pcirst# assertion on pci. 0 = bridge de-asserts pcirst# 1 = bridge asserts pcirst#. when pcirst # is asserted, the delayed transaction buffers, posting buffers, and the pci bus ar e initialized back to reset conditions. the rest of the part and the config uration registers are not affected. 5 master abort mode (mam ) ? r/w. this bit controls the ich10 pci bridge?s behavior when a master abort occurs: master abort on (g)mch/ich10 interconnect (dmi): 0 = bridge asserts trdy# on pci. it drives all 1s for read s, and discards data on writes. 1 = bridge returns a target abort on pci. master abort pci (non-locked cycles): 0 = normal completion status will be re turned on the (g)mch/ich10 interconnect. 1 = target abort completion status will be returned on the (g)mch/ich10 interconnect. note: all locked reads will return a completer abort completion status on the (g)mch/ ich10 interconnect. 4 vga 16-bit decode (v16d) ? r/w. this bit enables the ich10 pci bridge to provide 16-bits decoding of vga i/o address preclu ding the decode of vga alias addresses every 1 kb. this bit requires the vg ae bit in this register be set. http://www..net/ datasheet pdf - http://www..net/ pci-to-pci bridge registers (d30:f0) 366 datasheet 11.1.20 spdh?secondary pci device hiding register (pci-pci?d30:f0) offset address: 40h?41h attribute: r/w, ro default value: 0000h size: 16 bits this register allows software to hide the pci devices, either plugged into slots or on the motherboard. 3 vga enable (vgae) ? r/w. when set to a 1, the ich10 pci bridge forwards the following transactions to pci regardless of th e value of the i/o base and limit registers. the transactions are qualified by cm d.mse (d30:f0:04 bit 1) and cmd.iose (d30:f0:04 bit 0) being set. ? memory addresses: 000a0000h-000bffffh ? i/o addresses: 3b0h-3bbh and 3c0h-3dfh. for the i/o addresses, bits [63:16] of the address must be 0, and bits [15:10] of the address are ignored (i.e., aliased). the same holds true from secondary accesses to the primary interface in reverse. that is, when the bit is 0, memory and i/o a ddresses on the second ary interface between the above ranges will be claimed. 2 isa enable (ie) ? r/w. this bit only applies to i/ o addresses that are enabled by the i/o base and i/o limit registers and are in the fi rst 64 kb of pci i/o space. if this bit is set, the ich10 pci bridge will block any fo rwarding from primary to secondary of i/o transactions addressing the last 768 bytes in each 1-kb block (o ffsets 100h to 3ffh). 1 serr# enable (see) ? r/w. this bit controls the forwarding of secondary interface serr# assertions on the prim ary interface. when set, th e pci bridge will forward serr# pin. ? serr# is asserted on the secondary interface. ? this bit is set. ? cmd.see (d30:f0:04 bit 8) is set. 0 parity error response enable (pere) ? r/w. 0 = disable 1 = the ich10 pci bridge is en abled for parity error reportin g based on parity errors on the pci bus. bit description bit description 15:4 reserved 3 hide device 3 (hd3) ? r/w, ro. same as bit 0 of th is register, except for device 3 (ad[19]) 2 hide device 2 (hd2) ? r/w, ro. same as bit 0 of this register, except for device 2 (ad[18]) 1 hide device 1 (hd1) ? r/w, ro. same as bit 0 of this regi ster, except for device 1 (ad[17]) 0 hide device 0 (hd0) ? r/w, ro. 0 = the pci configuration cycles for this slot are not affected. 1 = intel ? ich10 hides device 0 on the pci bus. this is done by masking the idsel (keeping it low) for configuration cycles to that device. since the device will not see its idsel go active, it will not respond to pci configuration cycles and the processor will think the device is not presen t. ad[16] is used as idsel for device 0. http://www..net/ datasheet pdf - http://www..net/ datasheet 367 pci-to-pci bridge registers (d30:f0) 11.1.21 dtc?delayed transa ction control register (pci-pci?d30:f0) offset address: 44h ? 47h attribute: r/w default value: 00000000h size: 32 bits bit description 31 discard delayed transactions (ddt) ? r/w. 0 = logged delayed transactions are kept. 1 = the ich10 pci bridge will discard any delayed transactions it has logged. this includes transactions in th e pending queue, and any transactions in the active queue, whether in the hard or soft dt st ate. the prefetchers will be disabled and return to an idle state. notes: if a transaction is running on pci at the time this bit is set, that transaction will continue until either the pci master di sconnects (by de-asserting frame#) or the pci bridge disconnects (by asserting stop#). this bit is cleared by the pci bridge when the delayed transaction queu es are empty and have returned to an idle state. software sets this bit and polls for its completion 30 block delayed transactions (bdt) ? r/w. 0 = delayed transactions accepted 1 = the ich10 pci bridge will not accept incoming transactions which will result in delayed transactions. it will blindly retr y these cycles by asserting stop#. all postable cycles (memory writes) will still be accepted. 29:8 reserved 7:6 maximum delayed transactions (mdt) ? r/w. this field controls the maximum number of delayed transactions that the ich10 pci bridge will run. encodings are: 00 =) 2 active, 5 pending 01 =) 2 active, no pending 10 =) 1 active, no pending 11 =) reserved 5 reserved 4 auto flush after disco nnect enable (afade) ? r/w. 0 = the pci bridge will retain any fetched da ta until required to discard by producer/ consumer rules. 1 = the pci bridge will flush any prefetched data after either the pci master (by de- asserting frame#) or the pci bridge (b y asserting stop#) disconnects the pci transfer. 3 never prefetch (np) ? r/w. 0 = prefetch enabled 1 = the ich10 will only fetch a single dw and will not enable prefetching, regardless of the command being an memory read (mr), memory read line (mrl), or memory read multiple (mrm). http://www..net/ datasheet pdf - http://www..net/ pci-to-pci bridge registers (d30:f0) 368 datasheet 11.1.22 bps?bridge proprietary status register (pci-pci?d30:f0) offset address: 48h ? 4bh attribute: r/wc, ro default value: 00000000h size: 32 bits 2 memory read multiple prefetch disable (mrmpd) ? r/w. 0 = mrm commands will fetch multiple ca che lines as defined by the prefetch algorithm. 1 = memory read multiple (mrm) commands wi ll fetch only up to a single, 64-byte aligned cache line. 1 memory read line prefetch disable (mrlpd) ? r/w. 0 = mrl commands will fetch multiple cache lines as defined by the prefetch algorithm. 1 = memory read line (mrl) commands will fe tch only up to a single, 64-byte aligned cache line. 0 memory read prefetch disable (mrpd) ? r/w. 0 = mr commands will fetch up to a 64-byte aligned cache line. 1 = memory read (mr) commands will fetch only a single dw. bit description bit description 31:17 reserved 16 perr# assertion detected (pad) ? r/wc. this bit is set by hardware whenever the perr# pin is asserted on the ri sing edge of pci clock. this includes cases in which the chipset is the agent driving perr#. it re mains asserted until cleared by software writing a 1 to this location. when enabled by the perr#-to-serr# enable bit (in the bridge policy configuration regi ster), a 1 in this bit can generate an internal serr# and be a source for the nmi logic. this bit can be used by software to de termine the source of a system problem. 15:7 reserved 6:4 number of pending transactions (npt) ? ro. this field indicates to debug software how many transactions are in the pending queue. possible values are: 000 = no pending transaction 001 = 1 pending transaction 010 = 2 pending transactions 011 = 3 pending transactions 100 = 4 pending transactions 101 = 5 pending transactions 110 - 111 = reserved note: this field is not valid if dtc.mdt (offset 44h:bits 7:6) is any value other than ?00?. 3:2 reserved 1:0 number of active transactions (nat) ? ro. this field indica tes to debug software how many transactions are in the ac tive queue. possible values are: 00 = no active transactions 01 = 1 active transaction 10 = 2 active transactions 11 = reserved http://www..net/ datasheet pdf - http://www..net/ datasheet 369 pci-to-pci bridge registers (d30:f0) 11.1.23 bpc?bridge policy configuration register (pci-pci?d30:f0) offset address: 4ch ? 4fh attribute: r/w default value: 00001200h size: 32 bits bit description 31:14 reserved 13:8 upstream read latency threshold (urlt) ? r/w: this field specifies the number of pci clocks after internally enqueuing an upstream memory read request at which point the pci target logic should insert wait states in order to optimize lead-off latency. when the master returns after this thre shold has been reached and data has not arrived in the delayed transaction completion queue, then the pci target logic will insert wait states instead of immediately re trying the cycle. the pci target logic will insert up to 16 clocks of target initial latency (from frame# assertion to trdy# or stop# assertion) before retrying the pci re ad cycle (if the read data has not arrived yet). note that the starting event for this read latency timer is not explicitly visible externally. a value of 0h disables this policy completely such that wait states will never be inserted on the read lead-off data phase. the default value (12h) specifies 18 pci clocks (540 ns) and is a pproximately 4 clocks less than the typical idle lead-off latency expected for desktop ich10 systems. this value may need to be changed by bios, depending on the platform. 7 subtractive decode policy (sdp) ? r/w. 0 = the pci bridge always forwards memory and i/o cycles that are not claimed by any other device on the backbone (primary interface) to the pci bus (secondary interface). 1 = the pci bridge will not claim and forwar d memory or i/o cycles at all unless the corresponding space enable bit is set in the command register. note: the boot bios destination selection strap can force the bios accesses to pci. 6 perr#-to-serr# enable (pse) ? r/w. when this bit is set, a 1 in the perr# assertion status bit (in the bri dge proprietary status register) will result in an internal serr# assertion on the primary side of th e bridge (if also enabled by the serr# enable bit in the primary command re gister). serr# is a source of nmi. 5 secondary discard timer testmode (sdtt) ? r/w. 0 = the secondary discard timer expiration will be defined in bctrl.sdt (d30:f0:3e, bit 9) 1 = the secondary discard timer wi ll expire after 128 pci clocks. 4:3 reserved cmd.mse bpc.sdp range forwarding policy 00don?t care forward unclaimed cycles 0 1 don?t care forwarding prohibited 1xwithin range positive decode and forward 1xoutside subtractive decode & forward http://www..net/ datasheet pdf - http://www..net/ pci-to-pci bridge registers (d30:f0) 370 datasheet 11.1.24 svcap?subsystem vend or capability register (pci-pci?d30:f0) offset address: 50h ? 51h attribute: ro default value: 000dh size: 16 bits 11.1.25 svid?subsystem vendor ids register (pci-pci?d30:f0) offset address: 54h ? 57h attribute: r/wo default value: 00000000h size: 32 bits 2 peer decode enable (pde) ? r/w. 0 = the pci bridge assumes th at all memory cycles target main memory, and all i/o cycles are not claimed. 1 = the pci bridge will perform peer decode on any memory or i/o cycle from pci that falls outside of the memory and i/o window registers 1reserved 0 received target abort serr# enable (rtae) ? r/w. when set, the pci bridge will report serr# when psts.rta (d30:f0:06 bit 12) or ssts.rta (d30:f0:1e bit 12) are set, and cmd.see (d30:f0:04 bit 8) is set. bit description bit description 15:8 next capability (next) ? ro. value of 00h indicates this is the last item in the list. 7:0 capability identifier (cid) ? ro. value of 0dh indicates this is a pci bridge subsystem vendor capability. bit description 31:16 subsystem identifier (sid) ? r/wo. this field indicates the subsystem as identified by the vendor. this field is write once and is locked down until a bridge reset occurs (not the pci bus reset). 15:0 subsystem vendor identifier (svid) ? r/wo. this field indicates the manufacturer of the subsystem. this field is write once an d is locked down until a bridge reset occurs (not the pci bus reset). http://www..net/ datasheet pdf - http://www..net/ datasheet 371 gigabit lan configuration registers 12 gigabit lan configuration registers 12.1 gigabit lan configuration registers (gigabit lan ? d25:f0) note: register address locations that are not shown in table 12-1 should be treated as reserved. / table 12-1. gigabit lan configuration registers address map (gigabit lan ?d25:f0) (sheet 1 of 2) offset mnemonic register name default type 00h?01h vid vendor identification 8086h ro 02h?03h did device identification see register description ro 04h?05h pcicmd pci command 0000h r/w, ro 06h?07h pcists pci status 0010h r/wc, ro 08h rid revision identification see register description ro 09h?0bh cc class code 020000h ro 0ch cls cache line size 00h r/w 0dh plt primary latency timer 00h ro 0eh headtyp header type 00h ro 10h?13h mbara memory base address a 00000000h r/w, ro 14h?17h mbarb memory base address b 00000000h r/w, ro 18h?1bh mbarc memory base address c 00000001h r/w, ro 2ch?2dh sid subsystem id see register description ro 2eh?2fh svid subsystem vendor id see register description ro 30h?33h erba expansion rom base address see register description ro 34h capp capabilities list pointer c8h ro 3ch?3dh intr interrupt information see register description r/w, ro 3eh mlmg maximum latency/minimum grant 00h ro c8h?c9h clist1 capabilities list 1 d001h ro cah?cbh pmc pci power management capability see register description ro cch?cdh pmcs pci power management control and status see register description r/wc, r/w, ro http://www..net/ datasheet pdf - http://www..net/ gigabit lan configuration registers 372 datasheet 12.1.1 vid?vendor identi fication register (gigabit lan?d25:f0) address offset: 00h ? 01h attribute: ro default value: 8086h size: 16 bits 12.1.2 did?device identi fication register (gigabit lan?d25:f0) address offset: 02h?03h attribute: ro default value: see bit description size: 16 bits cfh dr data register see register description ro d0h?d1h clist2 capabilities list 2 e005h r/wo, ro d2h?d3h mctl message control 0080h r/w, ro d4h?d7h maddl message address low see register description r/w d8h?dbh maddh message address high see register description r/w dch?ddh mdat message data see register description r/w e0h?e1h flrcap function level reset capability 0009h ro e2h?e3h flrclv function level re set capability length and value see register description r/wo, ro e4h?e5h devctrl device control 0000h r/w, ro table 12-1. gigabit lan config uration registers address map (gigabit lan ?d25:f0) (sheet 2 of 2) offset mnemonic register name default type bit description 15:0 vendor id ? ro. this is a 16-bit value assigned to intel. the field may be auto-loaded from the nvm at address 0eh during init ti me depending on the "load vendor/device id" bit field in nvm word 0ah with a default value of 8086h. bit description 15:0 device id ? ro. this is a 16-bit value assigned to the intel ? ich10 gigabit lan controller. the field may be auto-loaded from the nvm word 0dh during initialization time depending on the "load vendor/d evice id" bit field in nvm word 0ah. http://www..net/ datasheet pdf - http://www..net/ datasheet 373 gigabit lan configuration registers 12.1.3 pcicmd?pci command register (gigabit lan?d25:f0) address offset: 04h?05h attribute: r/w, ro default value: 0000h size: 16 bits bit description 15:11 reserved 10 interrupt disable ? r/w. this disables pin-based intx# interrupts on enabled hot- plug and power management events. this bit has no e ffect on msi operation. 0 = internal intx# messages are generated if there is an interrupt for hot-plug or power management and msi is not enabled. 1 = internal intx# messages will not be generated. this bit does not affect inte rrupt forwarding from devices connected to the root port. assert_intx and deassert_intx messages wi ll still be forwarded to the internal interrupt controllers if this bit is set. 9 fast back to back enable (fbe) ? ro. hardwired to 0. 8 serr# enable (see) ? r/w. 0 = disable 1 = enables the gb lan controller to gene rate an serr# message when psts.sse is set. 7 wait cycle control (wcc) ? ro. hardwired to 0. 6 parity error response (per) ? r/w. 0 = disable. 1 = indicates that the device is capable of reporting pa rity errors as a master on the backbone . 5 palette snoop enable (pse) ? ro. hardwired to 0. 4 postable memory write enable (pmwe) ? ro. hardwired to 0. 3 special cycle enable (sce) ? ro. hardwired to 0. 2 bus master enable (bme) ? r/w. 0 = disable. all cycles from the device are master aborted 1 = enable. allows the root port to forwar d cycles onto the backbone from a gigabit lan* device. 1 memory space enable (mse) ? r/w. 0 = disable. memory cycles within the rang e specified by the memory base and limit registers are master aborted on the backbone. 1 = enable. allows memory cycles within th e range specified by the memory base and limit registers can be forwarde d to the gigabi t lan device. 0 i/o space enable (iose) ? r/w. this bit controls access to the i/o space registers. 0 = disable. i/o cycles within the range spec ified by the i/o base and limit registers are master aborted on the backbone. 1 = enable. allows i/o cycles within the range specified by the i/o base and limit registers can be forwarded to the gigabit lan device. http://www..net/ datasheet pdf - http://www..net/ gigabit lan configuration registers 374 datasheet 12.1.4 pcists?pci status register (gigabit lan?d25:f0) address offset: 06h ? 07h attribute: r/wc, ro default value: 0010h size: 16 bits bit description 15 detected parity error (dpe) ? r/wc. 0 = no parity error detected. 1 = set when the gb lan controller receiv es a command or data from the backbone with a parity error. this is set even if pcimd.per (d25:f0, bit 6) is not set. 14 signaled system error (sse) ? r/wc. 0 = no system error signaled. 1 = set when the gb lan controller signals a system error to the internal serr# logic. 13 received master abort (rma) ? r/wc. 0 = root port has not received a completion with unsupported re quest status from the backbone. 1 = set when the gb lan controller receiv es a completion with unsupported request status from the backbone. 12 received target abort (rta) ? r/wc. 0 = root port has not received a completion with completer abort from the backbone. 1 = set when the gb lan controller receiv es a completion with completer abort from the backbone. 11 signaled target abort (sta) ? r/wc. 0 = no target abort received. 1 = set whenever the gb lan controller fo rwards a target abort received from the downstream device onto the backbone. 10:9 devsel# timing status (dev_sts) ? ro. hardwired to 0. 8 master data parity error detected (dped) ? r/wc. 0 = no data parity error received. 1 = set when the gb lan controller receives a completion with a data parity error on the backbone and pcimd.per (d25:f0, bit 6) is set. 7 fast back to back capable (fb2bc) ? ro. hardwired to 0. 6reserved 5 66 mhz capable ? ro. hardwired to 0. 4 capabilities list ? ro. hardwired to 1. indi cates the presence of a capabilities list. 3 interrupt status ? ro. indicates status of ho t-plug and power management interrupts on the root port that re sult in intx# message generation. 0 = interrupt is deasserted. 1 = interrupt is asserted. this bit is not set if msi is enabled. if msi is not enabled, this bit is set regardless of the state of pcicmd.interrupt disable bit (d25:f0:04h:bit 10). 2:0 reserved http://www..net/ datasheet pdf - http://www..net/ datasheet 375 gigabit lan configuration registers 12.1.5 rid?revision identification register (gigabit lan?d25:f0) offset address: 08h attribute: ro default value: see bit description size: 8 bits 12.1.6 cc?class code register (gigabit lan?d25:f0) address offset: 09h ? 0bh attribute: ro default value: 020000h size: 24 bits 12.1.7 cls?cache line size register (gigabit lan?d25:f0) address offset: 0ch attribute: r/w default value: 00h size: 8 bits 12.1.8 plt?primary late ncy timer register (gigabit lan?d25:f0) address offset: 0dh attribute: ro default value: 00h size: 8 bits 12.1.9 ht?header type register (gigabit lan?d25:f0) address offset: 0eh attribute: ro default value: 00h size: 8 bits bit description 7:0 revision id ? ro. refer to the intel ? i/o controller hub (ich10) family specification update for the value of the revision id register bit description 23:0 class code ? ro. identifies the device as an ethernet adapter. 020000h = ethernet adapter. bit description 7:0 cache line size ? r/w. this field is implemented by pci devices as a read write field for legacy compatibility purposes but has no impact on any de vice functionality. bit description 7:0 latency timer (lt) ? ro. hardwired to ?0?. bit description 7:0 header type (ht) ? ro. 00h = indicates this is a single function device. http://www..net/ datasheet pdf - http://www..net/ gigabit lan configuration registers 376 datasheet 12.1.10 mbara?memory base address register a (gigabit lan?d25:f0) address offset: 10h ? 13h attribute: r/w, ro default value: 00000000h size: 32 bits the internal csr registers and memories are accessed as direct memory mapped offsets from the base address register. sw may only access whole dword at a time. 12.1.11 mbarb?memory base address register b (gigabit lan?d25:f0) address offset: 14h ? 17h attribute: r/w, ro default value: 00000000h size: 32 bits the internal registers that are used to access the lan space in the external flash device. access to these registers are direct memory mapped offsets from the base address register. software may only access a dword at a time. bit description 31:17 base address (ba) ? r/w . software programs this fiel d with the base address of this region. 16:4 memory size (msize) ? r/w . memory size is 128 kb. 3 prefetchable memory (pm) ? ro. the gbe lan controller does not implement prefetchable memory. 2:1 memory type (mt) ? ro. set to 00b indicating a 32 bit bar. 0 memory / io space (mios) ? ro. set to ?0? indicating a memory space bar. bit description 31:12 base address (ba) ? r/w . software programs this fiel d with the base address of this region. 11:4 memory size (msize) ? r/w . memory size is 4 kb. 3 prefetchable memory (pm) ? ro. the gb lan controller does not implement prefetchable memory. 2:1 memory type (mt) ? ro. set to 00b indicating a 32 bit bar. 0 memory / io space (mios) ? ro. set to ?0? indicating a memory space bar. http://www..net/ datasheet pdf - http://www..net/ datasheet 377 gigabit lan configuration registers 12.1.12 mbarc?memory base address register c (gigabit lan?d25:f0) address offset: 18h ? 1bh attribute: r/w, ro default value: 00000001h size: 32 bits internal registers, and memories, can be accessed using i/o operations. there are two 4b registers in the io mapping window: addr reg and data reg. sw may only access a dword at a time. 12.1.13 svid?subsystem vendor id register (gigabit lan?d25:f0) address offset: 2ch ? 2dh attribute: ro default value: see bit description size: 16 bits 12.1.14 sid?subsys tem id register (gigabit lan?d25:f0) address offset: 2eh ? 2fh attribute: ro default value: see bit description size: 16 bits 12.1.15 erba?expansion ro m base address register (gigabit lan?d25:f0) address offset: 30h ? 33h attribute: ro default value: see bit description size: 32 bits bit description 31:5 base address (ba) ? r/w . software programs this fiel d with the base address of this region. 4:1 i/o size (iosize) ? ro. i/o space size is 32 bytes. 0 memory / io space (mios) ? ro. set to ?1? indicating an i/o space bar. bit description 15:0 subsystem vendor id (svid) ? ro. this value may be loaded automatically from the nvm word 0ch upon power up depending on the "load subsystem id" bit field in nvm word 0ah. a value of 8086h is default fo r this field upon power up if the nvm does not respond or is not programmed. all func tions are initialized to the same value. bit description 15:0 subsystem id (sid) ? ro. this value may be loaded automatically from the nvm word 0bh upon power up or reset dependin g on the ?load subsystem id? bit field in nvm word 0ah with a default value of 0000h. this value is loadable from nvm word location 0bh. bit description 32:0 expansion rom base address (erba) ? ro. this register is used to define the address and size information for boot-time ac cess to the optional flash memory. if no flash memory exists this register reports 00000000h. http://www..net/ datasheet pdf - http://www..net/ gigabit lan configuration registers 378 datasheet 12.1.16 capp?capabilities list pointer register (gigabit lan?d25:f0) address offset: 34h attribute: r0 default value: c8h size: 8 bits 12.1.17 intr?interrupt information register (gigabit lan?d25:f0) address offset: 3ch?3dh attribute: r/w, ro default value: 0100h size: 16 bits function level reset: no 12.1.18 mlmg?maximum latenc y/minimum grant register (gigabit lan?d25:f0) address offset: 3eh attribute: ro default value: 00h size: 8 bits 12.1.19 clist 1?capabilities list register 1 (gigabit lan?d25:f0) address offset: c8h?c9h attribute: ro default value: d001h size: 16 bits bit description 7:0 capabilities pointer (ptr) ? ro. indicates that the pointe r for the first entry in the capabilities list is at c8h in configuration space. bit description 15:8 interrupt pin (ipin) ? ro. indicates the interrupt pin driven by the gb lan controller. 01h = the gb lan controller implem ents legacy interrupts on inta. 7:0 interrupt line (iline) ? r/w. default = 00h. software written value to indicate which interrupt line (vector) the interrupt is connected to. no hardware action is taken on this register. bit description 7:0 maximum latency/minimum grant (mlmg) ? ro. not used. hardwired to 00h. bit description 15:8 next capability (next) ? ro. value of d0h indicates the location of the next pointer. 7:0 capability id (cid) ? ro. indicates the linked list item is a pci power management register. http://www..net/ datasheet pdf - http://www..net/ datasheet 379 gigabit lan configuration registers 12.1.20 pmc?pci power manageme nt capabilities register (gigabit lan?d25:f0) address offset: cah ? cbh attribute: ro default value: see bit descriptions size: 16 bits function level reset: no (bits 15:11 only) bit description 15:11 pme_support (pmes) ? ro. this five-bit field indicates the power states in which the function may assert pm e#. it depend on pm ena and au x-pwr bits in word 0ah in the nvm: these bits are not reset by function level reset. 10 d2_support (d2s) ? ro. the d2 state is not supported. 9 d1_support (d1s) ? ro. the d1 state is not supported. 8:6 aux_current (ac) ? ro. required current defined in the data register. 5 device specific initialization (dsi) ? ro. set to ?1?. the gbe lan controller requires its device driver to be executed fo llowing transition to the d0 un-initialized state. 4 reserved 3 pme clock (pmec) ? ro. hardwired to ?0?. 2:0 version (vs) ? ro. hardwired to 010b to indicate support for revision 1.1 of the pci power management specification . condition function value pm ena=0 no pme at all states 0000b pm ena & aux-pwr=0 pme at d0 and d3hot 01001b pm ena & aux-pwr=1 pme at d0, d3hot and d3cold 11001b http://www..net/ datasheet pdf - http://www..net/ gigabit lan configuration registers 380 datasheet 12.1.21 pmcs?pci power mana gement control and status register (gigabit lan?d25:f0) address offset: cch ? cdh attribute: r/wc, r/w, ro default value: see bit description size: 16 bits function level reset: no (bit 8 only) bit description 15 pme status (pmes) ? r/wc. this bit is set to ?1? wh en the function detects a wake- up event independent of the state of the pmee bit. writing a ?1? will clear this bit. 14:13 data scale (dsc) ? r/w. this field indicates the sc aling factor to be used when interpreting the value of the data register. for the gbe lan and common functions this fi eld equals 01b (indicating 0.1 watt units) if the pm is enabled in the nvm, and the data_s elect field is set to 0, 3, 4, 7, (or 8 for function 0). else it equals 00b. for the manageability functions this field eq uals 10b (indicating 0.01 watt units) if the pm is enabled in the nvm, and the data_select fi eld is set to 0, 3, 4, 7. else it equals 00b. 12:9 data select (dsl) ? r/w. this four-bit field is used to select which data is to be reported through the data register (offset cfh) and data_scale fi eld. these bits are writeable only when the power management is enabled via nvm. 0h = d0 power consumption 3h = d3 power consumption 4h = d0 power dissipation 7h = d3 power dissipation 8h = common power all other values are reserved. 8 pme enable (pmee) ? r/w. if power management is enabled in the nvm, writing a ?1? to this register will enable wakeup. if power management is di sabled in the nvm, writing a ?1? to this bit has no affect, and will not set the bit to ?1?. this bit is not reset by function level reset. 7:2 reserved - returns a value of ?000000?. 1:0 power state (ps) ? r/w. this field is used both to determine the current power state of the gbe lan controller and to se t a new power state. the values are: 00 = d0 state (default) 01 = ignored 10 = ignored 11 = d3 state (power management must be enables in the nvm or this cycle will be ignored). http://www..net/ datasheet pdf - http://www..net/ datasheet 381 gigabit lan configuration registers 12.1.22 dr?data register (gigabit lan?d25:f0) address offset: cfh attribute: ro default value: see bit description size: 8 bits 12.1.23 clist 2?capabiliti es list register 2 (gigabit lan?d25:f0) address offset: d0h?d1h attribute: r/wo, ro default value: e005h size: 16 bits function level reset: no (bits 15:8 only) 12.1.24 mctl?message control register (gigabit lan?d25:f0) address offset: d2h?d3h attribute: r/w, ro default value: 0080h size: 16 bits bit description 7:0 reported data (rd) ? ro. this register is used to report power consumption and heat dissipation. this register is controlled by the data_select field in the pmcs (offset cch, bits 12:9), and the power scale is repo rted in the data_scale field in the pmcs (offset cch, bits 14:13). the data of this field is loaded from the nvm if pm is enabled in the nvm or with a default value of 00h otherwise. bit description 15:8 next capability (next) ? r/wo. value of e0h points to the function level reset capability structure. these bits are not reset by function level reset. 7:0 capability id (cid) ? ro. indicates the linked list item is a message signaled interrupt register. bit description 15:8 reserved 7 64-bit capable (cid) ? ro. set to ?1? to indicate that the gbe lan controller is capable of generating 64-bit message addresses. 6:4 multiple message enable (mme) ? ro. returns 000b to indicate that the gbe lan controller only supports a single message. 3:1 multiple message capable (mmc) ? ro. the gbe lan controller does not support multiple messages. 0 msi enable (msie) ? r/w. 0 = msi generation is disabled. 1 = the gb lan controller will generate ms i for interrupt assertion instead of intx signaling. http://www..net/ datasheet pdf - http://www..net/ gigabit lan configuration registers 382 datasheet 12.1.25 maddl?message address low register (gigabit lan?d25:f0) address offset: d4h?d7h attribute: r/w default value: see bit description size: 32 bits 12.1.26 maddh?message address high register (gigabit lan?d25:f0) address offset: d8h?dbh attribute: r/w default value: see bit description size: 32 bits 12.1.27 mdat?message data register (gigabit lan?d25:f0) address offset: dch?ddh attribute: r/w default value: see bit description size: 16 bits 12.1.28 flrcap?function level reset capability (gigabit lan?d25:f0) address offset: e0h?e1h attribute: ro default value: 0009h size: 16 bits bit description 31:0 message address low (maddl) ? r/w. written by the system to indicate the lower 32 bits of the address to use for the msi memory write transaction. the lower two bits will always return 0 regardless of the write operation. bit description 31:0 message address high (maddh) ? r/w. written by the system to indicate the upper 32 bits of the address to use for the msi memory write transaction. bit description 31:0 message data (mdat) ? r/w. written by the system to indicate the lower 16 bits of the data written in the msi memory write dw ord transaction. the upper 16 bits of the transaction are written as 0000h. bit description 15:8 next pointer ? ro. this field provides an offset to the next capability item in the capability list. the value of 00h in dicates the last item in the list. 7:0 capability id ? ro. the value of this field depends on the flrcssel bit. 13h = if flrcssel = 0 09h = if flrcssel = 1, indicating vendor specific capability. http://www..net/ datasheet pdf - http://www..net/ datasheet 383 gigabit lan configuration registers 12.1.29 flrclv?function level re set capability length and version (gigabit lan?d25:f0) address offset: e2h?e3h attribute: r/wo, ro default value: see description. size: 16 bits function level reset: no (bit s 9:8 only when flrcssel = 0) when flrcssel = 0, this register is defined as follows: when flrcssel = 1, this register is defined as follows: 12.1.30 devctrl?device control (gigabit lan?d25:f0) address offset: e4-e5h attribute: r/w, ro default value: 0000h size: 16 bits bit description 15:10 reserved. 9 function level reset capability ? r/wo. 1 = support for function level reset. this bit is not reset by function level reset. 8 txp capability ? r/wo. 1 = indicates support for the tr ansactions pending (txp) bit. txp must be supported if flr is supported. 7:0 capability length ? ro. the value of this field indi cates the number of bytes of the vendor specific capability as require by th e pci spec. it has the value of 06h for the function level reset capability. bit description 15:12 vendor specific capability id ? ro. a value of 2h in th is field identifies this capability as function level reset. 11:8 capability version ? ro. the value of this field indicates the version of the function level reset capability. default is 0h. 7:0 capability length ? ro. the value of this field indi cates the number of bytes of the vendor specific capability as require by th e pci spec. it has the value of 06h for the function level reset capability. bit description 15:9 reserved. 8 transactions pending (txp) ? r/w. 1 = indicates the controller has issued non-posted requests which have not been completed. 0 = indicates that completions for all no n-posted requests have been received. 7:1 reserved 0 initiate function level reset ? ro. this bit is used to initiate an flt transition. a write of ?1? initiates the transition. since hardware must not respond to any cycles until function level reset completion, the valu e read by software from this bit is 0. http://www..net/ datasheet pdf - http://www..net/ gigabit lan configuration registers 384 datasheet 12.2 mbara?gigabit lan ba se address a registers the internal csr registers and memories are accessed as direct memory mapped offsets from the base address register. this block is mapped into memory space, using the mbara base address register see section 12.1.10 . sw may only access whole dword at a time. 12.2.1 ldr4?lan device init ialization register 4 (gigabit lan memory mapped base address register) address offset: mbara + 0h attribute: ro default value: 14200100h size: 32 bits 12.2.2 ldr3?lan device init ialization register 3 (gigabit lan memory mapped base address register) address offset: mbara + 8h attribute: ro default value: 00080xxxh size: 32 bits table 12-2. gigabit lan base address a regi sters address map (gigabit lan? d25:f0) mbara+offset mnemonic register name default type 00?03h ldr4 lan device initialization 4 14200100h r/w 08?0bh ldr3 lan device initialization 3 00080xxxh ro 18?1bh ldcr2 lan device control 2 01500000h r/w 20?23h ldcr4 lan device control 4 1000xxxxh r/w f00h-f03h ldcr5 lan device control 5 00000000h r/w 3004?3007h ldr2 lan device initialization 2 b2b577cch r/w 3024-3027h ldr1 lan device initialization 1 600060006h r/w bit description 31:25 reserved 24 ldr4 field 1 ? r/w. bios may set this bit to 1. 23:0 reserved bit description 31 ldr3 field 1 ? ro. when set, this bit enable s the automatic reduction of dma frequency. this bit is loaded from word 13h in the nvm. 30:0 reserved http://www..net/ datasheet pdf - http://www..net/ datasheet 385 gigabit lan configuration registers 12.2.3 ldcr2?lan device control register 2 (gigabit lan memory mapped base address register) address offset: mbara + 18h attribute: r/w default value: 01500000h size: 32 bits 12.2.4 ldcr4?lan device control register 4 (gigabit lan memory mapped base address register) address offset: mbara + 20h attribute: r/w default value: 1000xxxxh size: 32 bits 12.2.5 ldr5?lan device control register 5 (gigabit lan memory mapped base address register) address offset: mbara + f00h attribute: r/w default value: 00000000h size: 32 bits 12.2.6 ldr1?lan device in itialization register 1 (gigabit lan memory mapped base address register) address offset: mbara + 3024h attribute: r/w default value: 60006006h size: 32 bits bit description 31:21 reserved 20 lan phy power down enable (lppde) ? r/w. when set, enables the phy to enter a low-power state when the lan controller is at the dmoff / d3 or dr and no wol. this bit is loaded from word 13h in the nvm. 19 ldcr2 field 1 ? r/w. this bit is loaded from word 13h in the nvm. 19:0 reserved bit description 31:0 bios may program this field. bit description 31:6 reserved 5 ldcr5 field 1 ? r/w. bios may set this bit. 4:0 reserved bit description 31:17 reserved 16 ldr1 field 1 ? r/w. bios must program this field to 1b. 15:0 reserved http://www..net/ datasheet pdf - http://www..net/ gigabit lan configuration registers 386 datasheet http://www..net/ datasheet pdf - http://www..net/ datasheet 387 lpc interface bridge registers (d31:f0) 13 lpc interface bridge registers (d31:f0) the lpc bridge function of the ich10 resides in pci device 31:function 0. this function contains many other functional units, such as dma and interrupt controllers, timers, power management, system management , gpio, rtc, and lpc configuration registers. registers and functions associated with othe r functional units (ehci, uhci, etc.) are described in their respective sections. 13.1 pci configuration registers (lpc i/f?d31:f0) note: address locations that are not shown should be treated as reserved. . table 13-1. lpc interface pci register address map (lpc i/f?d31:f0) (sheet 1 of 2) offset mnemonic register name default type 00h?01h vid vendor identification 8086h ro 02h?03h did device identification see register description ro 04h?05h pcicmd pci command 0007h r/w, ro 06h?07h pcists pci status 0210h r/wc, ro 08h rid revision identification see register description ro 09h pi programming interface 00h ro 0ah scc sub class code 01h ro 0bh bcc base class code 06h ro 0dh plt primary latency timer 00h ro 0eh headtyp header type 80h ro 2ch?2fh ss sub system identifiers 00000000h r/wo 40h?43h pmbase acpi base address 00000001h r/w, ro 44h acpi_cntl acpi control 00h r/w 48h?4bh gpiobase gpio base address 00000001h r/w, ro 4c gc gpio control 00h r/w 60h?63h pirq[ n ]_rout pirq[a?d] routing control 80808080h r/w 64h sirq_cntl serial irq control 10h r/w, ro 68h?6bh pirq[ n ]_rout pirq[e?h] routing control 80808080h r/w 6ch?6dh lpc_ibdf ioxapic bus:device:function 00f8h r/w 70h-71h h0bdf hpet 0 bus:device:function(h0bdf) 00f8h rw 72h-73h h1bdf hpet 1 bus:device:function(h1bdf) 00f8h rw http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 388 datasheet 74h-75h h2bdf hpet 2 bus:device:function(h2bdf) 00f8h rw 76h-77h h3bdf hpet 3 bus:device:function(h3bdf) 00f8h rw 78h-79h h4bdf hpet 4 bus:device:function(h4bdf) 00f8h rw 7ah-7bh h5bdf hpet 5 bus:device:function(h5bdf) 00f8h rw 7ch-7dh h6bdf hpet 6 bus:device:function(h6bdf) 00f8h rw 7eh-7fh h7bdf hpet 7 bus:device:function(h7bdf) 00f8h rw 80h lpc_i/o_dec i/o decode ranges 0000h r/w 82h?83h lpc_en lpc i/f enables 0000h r/w 84h?87h gen1_dec lpc i/f generic decode range 1 00000000h r/w 88h?8bh gen2_dec lpc i/f generic decode range 2 00000000h r/w 8ch?8eh gen3_dec lpc i/f generic decode range 3 00000000h r/w 90h?93h gen4_dec lpc i/f generic decode range 4 00000000h r/w 98h-9bh lgmr lpc generic memory range (corporate only) 00000000h r/w a0h?cfh power management (see section 13.8.1 ) d0h?d3h fwh_sel1 firmware hub select 1 00112233h r/w, ro d4h?d5h fwh_sel2 firmware hub select 2 4567h r/w d8h?d9h fwh_dec_en1 firmware hub decode enable 1 ffcfh r/w, ro dch bios_cntl bios control 00h r/wlo, r/w, ro e0h-e1h fdcap feature detection capability id 0009h ro e2h fdlen feature detection capability length 0ch ro e3h fdver feature detection version 10h ro e4h-ebh fdvct feature vector see description ro f0h-f3h rcba root complex base address 00000000h r/w table 13-1. lpc interface pci register addr ess map (lpc i/f?d31:f0) (sheet 2 of 2) offset mnemonic register name default type http://www..net/ datasheet pdf - http://www..net/ datasheet 389 lpc interface bridge registers (d31:f0) 13.1.1 vid?vendor identification register (lpc i/f?d31:f0) offset address: 00h ? 01h attribute: ro default value: 8086h size: 16-bit lockable: no power well: core 13.1.2 did?device identification register (lpc i/f?d31:f0) offset address: 02h ? 03h attribute: ro default value: see bit description size: 16-bit lockable: no power well: core 13.1.3 pcicmd?pci command re gister (lpc i/f?d31:f0) offset address: 04h ? 05h attribute: r/w, ro default value: 0007h size: 16-bit lockable: no power well: core bit description 15:0 vendor id ? ro. this is a 16-bit value assigned to intel. intel vid = 8086h bit description 15:0 device id ? ro. this is a 16-bit value assigned to the intel ? ich10 lpc bridge. refer to the intel ? i/o controller hu b (ich10) family for the value of the device id register. bit description 15:10 reserved 9 fast back to back enable (fbe) ? ro. hardwired to 0. 8 serr# enable (serr_en) ? r/w. the lpc bridge generate s serr# if this bit is set. 7 wait cycle control (wcc) ? ro. hardwired to 0. 6 parity error respon se enable (pere) ? r/w. 0 = no action is taken when detecting a parity error. 1 = enables the ich10 lpc bridge to respond to parity errors detected on backbone interface. 5 vga palette snoop (vps) ? ro. hardwired to 0. 4 memory write and invalidate enable (mwie) ? ro. hardwired to 0. 3 special cycle en able (sce) ? ro. hardwired to 0. 2 bus master enable (bme) ? ro. bus masters cannot be disabled. 1 memory space enable (mse) ? ro. memo ry space cannot be disabled on lpc. 0 i/o space enable (iose) ? ro. i/o space cannot be disabled on lpc. http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 390 datasheet 13.1.4 pcists?pci status re gister (lpc i/f?d31:f0) offset address: 06h ? 07h attribute: ro, r/wc default value: 0210h size: 16-bit lockable: no power well: core note: for the writable bits, software must write a 1 to clear bits that are set. writing a 0 to the bit has no effect. bit description 15 detected parity error (dpe) ? r/wc. this bit is set when the lpc bri dge detects a parity error on the internal backbone. the bit is set even if the pcicmd.pere bit (d31:f0:04, bit 6) is 0. 0 = parity error not detected. 1 = parity error detected. 14 signaled system error (sse) ? r/wc. this bit is set when the lpc bridge signals a system error to the internal serr# logic. 13 master abort status (rma) ? r/wc. 0 = unsupported request status not received. 1 = the bridge received a completion with unsupported request stat us from the backbone. 12 received target abort (rta) ? r/wc. 0 = completion abort not received. 1 = completion with completion ab ort received from the backbone. 11 signaled target abort (sta) ? r/wc. 0 = target abort not generated on the backbone. 1 = lpc bridge generated a completion pa cket with target abort status on the backbone. 10:9 devsel# timing status (dev_sts) ? ro. 01 = medium timing. 8 data parity error detected (dped) ? r/wc. 0 = all conditions listed below not met. 1 = set when all three of the following conditions are met: ? lpc bridge receives a completion pa cket from the backbone from a previous request, ? parity error has been detected (d31:f0:06, bit 15) ? pcicmd.pere bit (d31:f0 :04, bit 6) is set. 7 fast back to back capable (fbc): reserv ed ? bit has no meaning on the internal backbone. 6 reserved. 5 66 mhz capable (66mhz_cap) ? reserved ? bit has no meaning on the internal backbone. 4 capabilities list (clist) ? ro. capability list ex ists on the lpc bridge. 3 interrupt status (is) ? ro. the lpc bridge does not generate interrupts. 2:0 reserved. http://www..net/ datasheet pdf - http://www..net/ datasheet 391 lpc interface bridge registers (d31:f0) 13.1.5 rid?revision identification register (lpc i/f?d31:f0) offset address: 08h attribute: ro default value: see bit description size: 8 bits 13.1.6 pi?programming interface register (lpc i/f?d31:f0) offset address: 09h attribute: ro default value: 00h size: 8 bits 13.1.7 scc?sub class code register (lpc i/f?d31:f0) offset address: 0ah attribute: ro default value: 01h size: 8 bits 13.1.8 bcc?base clas s code register (lpc i/f?d31:f0) offset address: 0bh attribute: ro default value: 06h size: 8 bits 13.1.9 plt?primary la tency timer register (lpc i/f?d31:f0) offset address: 0dh attribute: ro default value: 00h size: 8 bits bit description 7:0 revision id (rid) ? ro. refer to the intel ? i/o controller hub (ich10) family specification update for the value of the revision id register bit description 7:0 programming interface ? ro. bit description 7:0 sub class code ? ro. 8-bit value that indicates th e category of bridge for the lpc bridge. 01h = pci-to-isa bridge. bit description 7:0 base class code ? ro. this field is an 8-bit value that indicates the type of device for the lpc bridge. 06h = bridge device. bit description 7:3 master latency count (mlc) ? reserved. 2:0 reserved. http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 392 datasheet 13.1.10 headtyp?header type register (lpc i/f?d31:f0) offset address: 0eh attribute: ro default value: 80h size: 8 bits 13.1.11 ss?sub system identifier s register (lpc i/f?d31:f0) offset address: 2ch ? 2fh attribute: r/wo default value: 00000000h size: 32 bits this register is initialized to logic 0 by th e assertion of pltrst#. this register can be written only once after pltrst# de-assertion. 13.1.12 pmbase?acpi base addres s register (lpc i/f?d31:f0) offset address: 40h ? 43h attribute: r/w, ro default value: 00000001h size: 32 bit lockable: no usage: acpi, legacy power well: core this register sets base address for acpi i/o registers, gpio registers, and tco i/o registers. these registers can be mapped anywhere in the 64-kb i/o space on 128-byte boundaries. bit description 7 multi-function device ? ro. this bit is 1 to indicate a multi-function device. 6:0 header type ? ro. this 7-bit field identifies the header layout of the configuration space. bit description 31:16 subsystem id (ssid) ? r/wo. this is written by bios. no hardware action taken on this value. 15:0 subsystem vendor id (ssvid) ? r/wo. this is written by bios. no hardware action taken on this value. bit description 31:16 reserved 15:7 base address ? r/w. this field provides 128 by tes of i/o space for acpi, gpio, and tco logic. this is placed on a 128-byte boundary. 6:1 reserved 0 resource type indicator (rte) ? ro. ha rdwired to 1 to indicate i/o space. http://www..net/ datasheet pdf - http://www..net/ datasheet 393 lpc interface bridge registers (d31:f0) 13.1.13 acpi_cntl?acpi control register (lpc i/f ? d31:f0) offset address: 44h attribute: r/w default value: 00h size: 8 bit lockable: no usage: acpi, legacy power well: core 13.1.14 gpiobase?gpio base ad dress register (lpc i/f ? d31:f0) offset address: 48h?4bh attribute: r/w, ro default value: 00000001h size: 32 bit bit description 7 acpi enable (acpi_en) ? r/w. 0 = disable. 1 = decode of the i/o range pointed to by th e acpi base register is enabled, and the acpi power management fu nction is enabled. no te that the apm power management ranges (b2/b3h) are always en abled and are not affected by this bit. 6:3 reserved 2:0 sci irq select (sci_irq_sel) ? r/w. specifies on which irq the sci will internally appear. if not using the apic, the sci must be routed to irq9?11, and that interrupt is not sharable with the serirq stream, but is shareable with other pci interrupts. if using the apic, the sci can also be mapped to irq20?23, and can be shared with other interrupts. when the interrupt is mapped to apic interrupts 9, 10, or 11, the apic should be programmed for active-high re ception. when the interrupt is mapped to apic interrupts 20 through 23, the apic should be programmed for active-low reception. bits sci map 000b irq9 001b irq10 010b irq11 011b reserved 100b irq20 (only available if apic enabled) 101b irq21 (only available if apic enabled) bit description 31:16 reserved. always 0. 15:7 base address (ba) ? rw . provides the 128 bytes of i/o space for gpio. 6:1 reserved. always 0 0 ro. hardwired to 1 to indicate i/o space. http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 394 datasheet 13.1.15 gc?gpio control register (lpc i/f ? d31:f0) offset address: 4ch attribute: r/w default value: 00h size: 8 bit bit description 7:5 reserved. 4 gpio enable (en) ? r/w. this bit enables/disables decode of the i/o range pointed to by the gpio base address register (d31:f0:48h) and enables the gpio function. 0 = disable. 1 = enable. 3:1 reserved. 0 gpio lockdown enable (gle) ? r/w. this bit enables lockdown of the following gpio registers: ? offset 00h: gpio_use_sel ? offset 04h: gp_io_sel ? offset 0ch: gp_lvl ? offset 30h: gpio_use_sel2 ? offset 34h: gp_io_sel2 ? offset 38h: gp_lvl2 ? offset 40h: gpio_use_sel3 (corporate only) ? offset 44h: gp_io_sel3 (corporate only) ? offset 48h: gp_lvl3 (corporate only) ? offset 60h: gp_rst_sel 0 = disable. 1 = enable. when this bit is written from a 1-to-0 an smi# is generate d, if enabled. this ensures that only smm code can change the above gp io registers after they are locked down. http://www..net/ datasheet pdf - http://www..net/ datasheet 395 lpc interface bridge registers (d31:f0) 13.1.16 pirq[n]_rout?pirq[a,b,c, d] routing control register (lpc i/f?d31:f0) offset address: pirqa ? 60h, pirqb ? 61h, attribute: r/w pirqc ? 62h, pirqd ? 63h default value: 80h size: 8 bit lockable: no power well: core bit description 7 interrupt routing enable (irqen) ? r/w. 0 = the corresponding pirq is routed to one of the isa-compatible interrupts specified in bits[3:0]. 1 = the pirq is not routed to the 8259. note: bios must program this bit to 0 during post for any of the pirqs that are being used. the value of this bit may subsequently be changed by the os when setting up for i/o apic interrupt delivery mode. 6:4 reserved 3:0 irq routing ? r/w. (isa compatible.) value irq value irq 0000b reserved 1000b reserved 0001b reserved 1001b irq9 0010b reserved 1010b irq10 0011b irq3 1011b irq11 0100b irq4 1100b irq12 0101b irq5 1101b reserved 0110b irq6 1110b irq14 0111b irq7 1111b irq15 http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 396 datasheet 13.1.17 sirq_cntl?serial irq control register (lpc i/f?d31:f0) offset address: 64h attribute: r/w, ro default value: 10h size: 8 bit lockable: no power well: core bit description 7 serial irq enable (sirqen) ? r/w. 0 = the buffer is input only and internally serirq will be a 1. 1 = serial irqs will be recognized. the se rirq pin will be configured as serirq. 6 serial irq mode select (sirqmd) ? r/w. 0 = the serial irq machine will be in quiet mode. 1 = the serial irq machine wi ll be in continuous mode. note: for systems using quiet mode, this bit sh ould be set to 1 (continuous mode) for at least one frame after coming out of reset before switching back to quiet mode. failure to do so will result in the ich10 not recognizing serirq interrupts. 5:2 serial irq frame size (sirqsz) ? ro. fixed field that indicates the size of the serirq frame as 21 frames. 1:0 start frame pulse width (sfpw) ? r/w. this is the number of pci clocks that the serirq pin will be driven low by the serial irq machine to signal a start frame. in continuous mode, the ich10 will drive th e start frame for the number of clocks specified. in quiet mode, the ich10 will driv e the start frame for the number of clocks specified minus one, as the first cl ock was driven by the peripheral. 00 = 4 clocks 01 = 6 clocks 10 = 8 clocks 11 = reserved http://www..net/ datasheet pdf - http://www..net/ datasheet 397 lpc interface bridge registers (d31:f0) 13.1.18 pirq[n]_rout?pirq[e,f,g, h] routing control register (lpc i/f?d31:f0) offset address: pirqe ? 68h, pirqf ? 69h, attribute: r/w pirqg ? 6ah, pirqh ? 6bh default value: 80h size: 8 bit lockable: no power well: core bit description 7 interrupt routing enable (irqen) ? r/w. 0 = the corresponding pirq is routed to on e of the isa-compatible interrupts specified in bits[3:0]. 1 = the pirq is not routed to the 8259. note: bios must program this bit to 0 during post for any of the pirqs that are being used. the value of this bit may su bsequently be changed by the os when setting up for i/o apic interrupt delivery mode. 6:4 reserved 3:0 irq routing ? r/w. (isa compatible.) value irq value irq 0000b reserved 1000b reserved 0001b reserved 1001b irq9 0010b reserved 1010b irq10 0011b irq3 1011b irq11 0100b irq4 1100b irq12 0101b irq5 1101b reserved 0110b irq6 1110b irq14 0111b irq7 1111b irq15 http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 398 datasheet 13.1.19 lpc_ibdf?ioxapic bus:device:function (lpc i/f?d31:f0) offset address: 6ch-6dh attribute: r/w default value: 00f8h size: 16 bit 13.1.20 lpc_hnbdf ? hpet n bu s:device:function (lpc i/f? d31:f0) offset address: h0bdf 70h-71h h1bdf 72h-73h h2bdf 74h-75h h3bdf 76h-77h h4bdf 78h-79h h5bdf 7ah-7bh h6bdf 7ch-7dh h7bdf 7eh-7fh attribute: r/w default value: 00f8h size: 16 bit bit description 15:0 ioxapic bus:device:function (ibdf) ? r/w. this field specifies the bus:device:function that ich10?s ioxa pic will be using for the following: ? as the requester id when initiating interrupt messages to the processor. ? as the completer id when responding to the reads targeting the ioxapic?s memory-mapped i/o registers. the 16-bit field comprises the following: this field defaults to bus 0: device 31: function 0 after reset. bios can program this field to provide a unique bus:device:function number for the internal ioxapic. bits description 15:8 bus number 7:3 device number 2:0 function number bit description 15:0 hpet n bus:device:function (hnbdf) ? r/w. this field specifies the bus:device:function that ich10?s hpet n will be using in the following: ? as the requester id when initiati ng interrupt messages to the cpu ? as the completer id when respon ding to the reads targeting the corresponding hpet?s memo ry-mapped i/o registers the 16-bit field comp rises the following: this field is default to bus 0: devi ce 31: function 0 after reset. bios shall program this field accordingly if unique bus:device:function number is required for the corresponding hpet. bits description 15:8 bus number 7:3 device number 2:0 function number http://www..net/ datasheet pdf - http://www..net/ datasheet 399 lpc interface bridge registers (d31:f0) 13.1.21 lpc_i/o_dec?i/o de code ranges register (lpc i/f?d31:f0) offset address: 80h attribute: r/w default value: 0000h size: 16 bit bit description 15:13 reserved 12 fdd decode range ? r/w. this bit determines wh ich range to decode for the fdd port. 0 = 3f0h ? 3f5h, 3f7h (primary) 1 = 370h ? 375h, 377h (secondary) 11:10 reserved 9:8 lpt decode range ? r/w. this field determines which range to decode for the lpt port. 00 = 378h ? 37fh and 778h ? 77fh 01 = 278h ? 27fh (port 279h is read only) and 678h ? 67fh 10 = 3bch ?3beh and 7bch ? 7beh 11 = reserved 7reserved 6:4 comb decode range ? r/w. this field determines which range to decode for the comb port. 000 = 3f8h ? 3ffh (com1) 001 = 2f8h ? 2ffh (com2) 010 = 220h ? 227h 011 = 228h ? 22fh 100 = 238h ? 23fh 101 = 2e8h ? 2efh (com4) 110 = 338h ? 33fh 111 = 3e8h ? 3efh (com3) 3reserved 2:0 coma decode range ? r/w. this field determines which range to decode for the coma port. 000 = 3f8h ? 3ffh (com1) 001 = 2f8h ? 2ffh (com2) 010 = 220h ? 227h 011 = 228h ? 22fh 100 = 238h ? 23fh 101 = 2e8h ? 2efh (com4) 110 = 338h ? 33fh 111 = 3e8h ? 3efh (com3) http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 400 datasheet 13.1.22 lpc_en?lpc i/f enables register (lpc i/f?d31:f0) offset address: 82h ? 83h attribute: r/w default value: 0000h size: 16 bit power well: core bit description 15:14 reserved 13 cnf2_lpc_en ? r/w. microcontroller enable #2. 0 = disable. 1 = enables the decoding of the i/o locati ons 4eh and 4fh to the lpc interface. this range is used for a microcontroller. 12 cnf1_lpc_en ? r/w. super i/o enable. 0 = disable. 1 = enables the decoding of the i/o locati ons 2eh and 2fh to the lpc interface. this range is used for super i/o devices. 11 mc_lpc_en ? r/w. microcontroller enable #1. 0 = disable. 1 = enables the decoding of the i/o location s 62h and 66h to the lpc interface. this range is used for a microcontroller. 10 kbc_lpc_en ? r/w. keyboard enable. 0 = disable. 1 = enables the decoding of the i/o location s 60h and 64h to the lpc interface. this range is used for a microcontroller. 9 gameh_lpc_en ? r/w. high gameport enable 0 = disable. 1 = enables the decoding of the i/o locations 208h to 20fh to the lpc interface. this range is used for a gameport. 8 gamel_lpc_en ? r/w. low gameport enable 0 = disable. 1 = enables the decoding of the i/o locations 200h to 207h to the lpc interface. this range is used for a gameport. 7:4 reserved 3 fdd_lpc_en ? r/w. floppy drive enable 0 = disable. 1 = enables the decoding of the fdd range to the lpc interface. this range is selected in the lpc_fdd/lpt decode range register (d31:f0:80h, bit 12). 2 lpt_lpc_en ? r/w. parallel port enable 0 = disable. 1 = enables the decoding of the lptrange to th e lpc interface. this range is selected in the lpc_fdd/lpt decode range register (d31:f0:80h, bit 9:8). 1 comb_lpc_en ? r/w. com port b enable 0 = disable. 1 = enables the decoding of the comb rang e to the lpc interface. this range is selected in the lpc_com decode rang e register (d31:f0:80h, bits 6:4). 0 coma_lpc_en ? r/w. com port a enable 0 = disable. 1 = enables the decoding of the coma ra nge to the lpc interface. this range is selected in the lpc_com decode rang e register (d31:f0:80h, bits 3:2). http://www..net/ datasheet pdf - http://www..net/ datasheet 401 lpc interface bridge registers (d31:f0) 13.1.23 gen1_dec?lpc i/f generi c decode range 1 register (lpc i/f?d31:f0) offset address: 84h ? 87h attribute: r/w default value: 00000000h size: 32 bit power well: core 13.1.24 gen2_dec?lpc i/f generi c decode range 2 register (lpc i/f?d31:f0) offset address: 88h ? 8bh attribute: r/w default value: 00000000h size: 32 bit power well: core bit description 31:24 reserved 23:18 generic i/o decode rang e address[7:2] mask ? r/w. a 1 in any bit position indicates that any value in the correspondin g address bit in a rece ived cycle will be treated as a match. the corresponding bit in the address field, belo w, is ignored. the mask is only provided for the lower 6 bits of the dword address, allowing for decoding blocks up to 256 bytes in size. 17:16 reserved 15:2 generic i/o decode range 1 base address (gen1_base) ? r/w. this address is aligned on a 128-byte boundary, and must have address lines 31:16 as 0. note: the ich does not provide decode do wn to the word or byte level. 1reserved 0 generic decode range 1 enable (gen1_en) ? r/w. 0 = disable. 1 = enable the gen1 i/o range to be forwarded to the lpc i/f. bit description 31:24 reserved 23:18 generic i/o decode rang e address[7:2] mask ? r/w. a 1 in any bit position indicates that any value in the correspondin g address bit in a rece ived cycle will be treated as a match. the corresponding bit in the address field, belo w, is ignored. the mask is only provided for the lower 6 bits of the dword address, allowing for decoding blocks up to 256 bytes in size. 17:16 reserved 15:2 generic i/o decode range 2 base address (gen1_base) ? r/w. note: the ich does not provide decode do wn to the word or byte level. 1reserved 0 generic decode range 2 enable (gen2_en) ? r/w. 0 = disable. 1 = enable the gen2 i/o range to be forwarded to the lpc i/f. http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 402 datasheet 13.1.25 gen3_dec?lpc i/f generi c decode range 3 register (lpc i/f?d31:f0) offset address: 8ch ? 8eh attribute: r/w default value: 00000000h size: 32 bit power well: core bit description 31:24 reserved 23:18 generic i/o decode range address[7:2] mask ? r/w. a 1 in any bit position indicates that any value in the corresponding address bit in a received cycle will be treated as a match. the corresponding bit in the address field, belo w, is ignored. the mask is only provided for the lower 6 bits of the dword address, allowing for decoding blocks up to 256 bytes in size. 17:16 reserved 15:2 generic i/o decode range 3 base address (gen3_base) ? r/w. note: the ich does not provide decode do wn to the word or byte level. 1 reserved 0 generic decode range 3 enable (gen3_en) ? r/w. 0 = disable. 1 = enable the gen3 i/o range to be forwarded to the lpc i/f. http://www..net/ datasheet pdf - http://www..net/ datasheet 403 lpc interface bridge registers (d31:f0) 13.1.26 gen4_dec?lpc i/f generi c decode range 4 register (lpc i/f?d31:f0) offset address: 90h ? 93h attribute: r/w default value: 00000000h size: 32 bit power well: core 13.1.27 lgmr ? lpc i/f generic memory range (lpc i/f? d31:f0) (corporate only) offset address: 98h ? 9bh attribute: r/w default value: 00000000h size: 32 bit power well: core bit description 31:24 reserved 23:18 generic i/o decode rang e address[7:2] mask ? r/w. a 1 in any bit position indicates that any value in the correspondin g address bit in a rece ived cycle will be treated as a match. the corresponding bit in the address field, belo w, is ignored. the mask is only provided for the lower 6 bits of the dword address, allowing for decoding blocks up to 256 bytes in size. 17:16 reserved 15:2 generic i/o decode range 4 base address (gen4_base) ? r/w. note: the ich does not provide decode do wn to the word or byte level. 1reserved 0 generic decode range 4 enable (gen4_en) ? r/w. 0 = disable. 1 = enable the gen4 i/o range to be forwarded to the lpc i/f. bit description 31:16 memory address[31:16] ? r/w. this field specif ies a 64 kb memory block anywhere in the 4 gb memory space that will be decoded to lpc as standard lpc memory cycle if enabled. 15:1 reserved 0 lpc memory range decode enable ? r/w. when this bit is set to 1, then the range specified in bits 31:16 of this regist er is enabled for decoding to lpc. http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 404 datasheet 13.1.28 fwh_sel1?firmware hub select 1 register (lpc i/f?d31:f0) offset address: d0h ? d3h attribute: r/w, ro default value: 00112233h size: 32 bits bit description 31:28 fwh_f8_idsel ? ro. idsel for two 512-kb firmware hub memory ranges and one 128-kb memory range. this field is fixed at 0000. the idsel programmed in this field addresses the following memory ranges: fff8 0000h ? ffff ffffh ffb8 0000h ? ffbf ffffh 000e 0000h ? 000f ffffh 27:24 fwh_f0_idsel ? r/w. idsel for two 512-kb firmware hub memory ranges. the idsel programmed in this field addr esses the following memory ranges: fff0 0000h ? fff7 ffffh ffb0 0000h ? ffb7 ffffh 23:20 fwh_e8_idsel ? r/w. idsel for two 512-kb firmware hub memory ranges. the idsel programmed in this field addr esses the following memory ranges: ffe8 0000h ? ffef ffffh ffa8 0000h ? ffaf ffffh 19:16 fwh_e0_idsel ? r/w. idsel for two 512-kb firmware hub memory ranges. the idsel programmed in this field addr esses the following memory ranges: ffe0 0000h ? ffe7 ffffh ffa0 0000h ? ffa7 ffffh 15:12 fwh_d8_idsel ? r/w. idsel for two 512-kb firmware hub memory ranges. the idsel programmed in this field addr esses the following memory ranges: ffd8 0000h ? ffdf ffffh ff98 0000h ? ff9f ffffh 11:8 fwh_d0_idsel ? r/w. idsel for two 512-kb firmware hub memory ranges. the idsel programmed in this field addr esses the following memory ranges: ffd0 0000h ? ffd7 ffffh ff90 0000h ? ff97 ffffh 7:4 fwh_c8_idsel ? r/w. idsel for two 512-kb firmware hub memory ranges. the idsel programmed in this field addr esses the following memory ranges: ffc8 0000h ? ffcf ffffh ff88 0000h ? ff8f ffffh 3:0 fwh_c0_idsel ? r/w. idsel for two 512-kb firmware hub memory ranges. the idsel programmed in this field addr esses the following memory ranges: ffc0 0000h ? ffc7 ffffh ff80 0000h ? ff87 ffffh http://www..net/ datasheet pdf - http://www..net/ datasheet 405 lpc interface bridge registers (d31:f0) 13.1.29 fwh_sel2?firmware hub select 2 register (lpc i/f?d31:f0) offset address: d4h ? d5h attribute: r/w default value: 4567h size: 16 bits bit description 15:12 fwh_70_idsel ? r/w. idsel for two, 1-m firmware hub memory ranges. the idsel programmed in this field a ddresses the following memory ranges: ff70 0000h ? ff7f ffffh ff30 0000h ? ff3f ffffh 11:8 fwh_60_idsel ? r/w. idsel for two, 1-m firmware hub memory ranges. the idsel programmed in this field a ddresses the following memory ranges: ff60 0000h ? ff6f ffffh ff20 0000h ? ff2f ffffh 7:4 fwh_50_idsel ? r/w. idsel for two, 1-m firmware hub memory ranges. the idsel programmed in this field a ddresses the following memory ranges: ff50 0000h ? ff5f ffffh ff10 0000h ? ff1f ffffh 3:0 fwh_40_idsel ? r/w. idsel for two, 1-m firmware hub memory ranges. the idsel programmed in this field a ddresses the following memory ranges: ff40 0000h ? ff4f ffffh ff00 0000h ? ff0f ffffh http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 406 datasheet 13.1.30 fwh_dec_en1?firmware hu b decode enable register (lpc i/f?d31:f0) offset address: d8h ? d9h attribute: r/w, ro default value: ffcfh size: 16 bits bit description 15 fwh_f8_en ? ro. this bit enables decoding two 512-kb firmware hub memory ranges, and one 128-kb memory range. 0 = disable 1 = enable the following ranges for the firmware hub fff80000h ? ffffffffh ffb80000h ? ffbfffffh 14 fwh_f0_en ? r/w. this bit enables decoding two 512-kb firmware hub memory ranges. 0 = disable. 1 = enable the following ranges for the firmware hub: fff00000h ? fff7ffffh ffb00000h ? ffb7ffffh 13 fwh_e8_en ? r/w. this bit enables decoding two 512-kb firmware hub memory ranges. 0 = disable. 1 = enable the following ranges for the firmware hub: ffe80000h ? ffeffffh ffa80000h ? ffafffffh 12 fwh_e0_en ? r/w. this bit enables decoding two 512-kb firmware hub memory ranges. 0 = disable. 1 = enable the following ranges for the firmware hub: ffe00000h ? ffe7ffffh ffa00000h ? ffa7ffffh 11 fwh_d8_en ? r/w. this bit enables decoding two 512-kb firmware hub memory ranges. 0 = disable. 1 = enable the following ranges for the firmware hub ffd80000h ? ffdfffffh ff980000h ? ff9fffffh 10 fwh_d0_en ? r/w. this bit enables decoding two 512-kb firmware hub memory ranges. 0 = disable. 1 = enable the following ranges for the firmware hub ffd00000h ? ffd7ffffh ff900000h ? ff97ffffh 9 fwh_c8_en ? r/w. this bit enables decoding two 512-kb firmware hub memory ranges. 0 = disable. 1 = enable the following ranges for the firmware hub ffc80000h ? ffcfffffh ff880000h ? ff8fffffh http://www..net/ datasheet pdf - http://www..net/ datasheet 407 lpc interface bridge registers (d31:f0) note: this register effects the bios decode regardless of whether th e bios is resident on lpc or spi. the concept of feature space does not apply to spi-based flash. the ich simply decodes these ranges as memory accesses when enabled for the spi flash interface. 8 fwh_c0_en ? r/w. this bit enables decoding two 512-kb firmware hub memory ranges. 0 = disable. 1 = enable the following ranges for the firmware hub ffc00000h ? ffc7ffffh ff800000h ? ff87ffffh 7 fwh_legacy_f_en ? r/w. this enables the decoding of the legacy 64kb range at f0000h ? fffffh. 0 = disable. 1 = enable the following legacy ranges for the firmware hub f0000h ? fffffh note: the decode for the bios legacy f segment is enabled only by this bit and is not affected by the gen_pmcon_1.ia64_en bit. 6 fwh_legacy_e_en ? r/w. this enables the decodi ng of the legacy 64kb range at e0000h ? effffh. 0 = disable. 1 = enable the following legacy ranges for the firmware hub e0000h ? effffh note: the decode for the bios legacy e segment is enabled only by this bit and is not affected by the gen_pmcon_1.ia64_en bit. 5:4 reserved 3 fwh_70_en ? r/w. enables decoding two 1- m firmware hub memory ranges. 0 = disable. 1 = enable the following ranges for the firmware hub ff70 0000h ? ff7f ffffh ff30 0000h ? ff3f ffffh 2 fwh_60_en ? r/w. enables decoding two 1- m firmware hub memory ranges. 0 = disable. 1 = enable the following ranges for the firmware hub ff60 0000h ? ff6f ffffh ff20 0000h ? ff2f ffffh 1 fwh_50_en ? r/w. enables decoding two 1- m firmware hub memory ranges. 0 = disable. 1 = enable the following ranges for the firmware hub ff50 0000h ? ff5f ffffh ff10 0000h ? ff1f ffffh 0 fwh_40_en ? r/w. enables decoding two 1- m firmware hub memory ranges. 0 = disable. 1 = enable the following ranges for the firmware hub ff40 0000h ? ff4f ffffh ff00 0000h ? ff0f ffffh bit description http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 408 datasheet 13.1.31 bios_cntl?bios control register (lpc i/f?d31:f0) offset address: dch attribute: r/wlo, r/w, ro default value: 00h size: 8 bit lockable: no power well: core bit description 7:5 reserved 4 top swap status (tss) ? ro. this bit provides a read-only path to view the state of the top swap bit that is at offset 3414h, bit 0. 3:2 spi read configuration (src) ? r/w. this 2-bit field controls two policies related to bios reads on th e spi interface: bit 3 = prefetch enable bit 2 = cache disable settings are summarized below: 1 bios lock enable (ble) ? r/wlo. 0 = setting the bioswe will not cause smis. 1 = enables setting the bioswe bit to cause smis. once set, this bit can only be cleared by a pltrst#. 0 bios write enable (bioswe) ? r/w. 0 = only read cycles result in firmware hub i/f cycles. 1 = access to the bios space is enabled for both read and write cycles. when this bit is written from a 0 to a 1 and bios lock en able (ble) is also set, an smi# is generated. this ensu res that only smi code can update bios. bits 3:2 description 00b no prefetching, but caching enabled. 64b demand reads load the read buffer cache with ?valid ? data, allowing repeated code fetches to the same line to complete quickly 01b no prefetching and no caching. one-to-one co rrespondence of host bios reads to spi cycles. this value can be used to invalidate the cache. 10b prefetching and caching enabled. this mode is used for long sequences of short reads to consecutive addresses (i.e., shadowing). 11b reserved. this is an invalid configuration , caching must be enabled when prefetching is enabled. http://www..net/ datasheet pdf - http://www..net/ datasheet 409 lpc interface bridge registers (d31:f0) 13.1.32 fdcap?feature dete ction capability id (lpc i/f?d31:f0) offset address: e0h-e1h attribute: ro default value: 0009h size: 16 bit power well: core 13.1.33 fdlen?feature detect ion capability length (lpc i/f?d31:f0) offset address: e2h attribute: ro default value: 0ch size: 8 bit power well: core 13.1.34 fdver?feature detection version (lpc i/f?d31:f0) offset address: e3h attribute: ro default value: 10h size: 8 bit power well: core bit description 15:8 next item pointer (next) ? ro. configuration offset of the next capability item. 00h indicates the last item in the capability list. 7:0 capability id ? ro. indicates a vendor specific capability. bit description 7:0 capability length ? ro. indicates the length of this vendor specific capability, as required by the pci specification. bit description 7:4 vendor-specific capability id ? ro. a value of 1h in this 4-bit field identifies this capability as feature detectio n type. this field allows so ftware to differentiate the feature detection capability from ot her vendor-specifi c capabilities. 3:0 capability version ? ro. this field indicates the version of the feature detection capability. http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 410 datasheet 13.1.35 fdvct?feature vector (lpc i/f?d31:f0) offset address: e4h-ebh attribute: ro default value: see description size: 64 bit power well: core 13.1.36 rcba?root complex base address register (lpc i/f?d31:f0) offset address: f0-f3h attribute: r/w default value: 00000000h size: 32 bit bit description 63:42 reserved 41 intel ? active management technology re lease 5.0 support capability ? ro. 0 = professional 1 = basic 40:38 reserved 37 intel active management te chnology capability ? ro. 0 = capable 1 = disabled 36:6 reserved 5 sata raid 0/1/5/10 capability? ro. 0 = capable 1 = disabled 4:0 reserved bit description 31:14 base address (ba) ? r/w. base address for the root complex register block decode range. this address is al igned on a 16-kb boundary. 13:1 reserved 0 enable (en) ? r/w. when set, enables the range specified in ba to be claimed as the root complex register block. http://www..net/ datasheet pdf - http://www..net/ datasheet 411 lpc interface bridge registers (d31:f0) 13.2 dma i/o registers (lpc i/f?d31:f0) table 13-2. dma registers (sheet 1 of 2) port alias register name default type 00h 10h channel 0 dma base & current address undefined r/w 01h 11h channel 0 dma base & current count undefined r/w 02h 12h channel 1 dma base & current address undefined r/w 03h 13h channel 1 dma base & current count undefined r/w 04h 14h channel 2 dma base & current address undefined r/w 05h 15h channel 2 dma base & current count undefined r/w 06h 16h channel 3 dma base & current address undefined r/w 07h 17h channel 3 dma base & current count undefined r/w 08h 18h channel 0?3 dma command undefined wo channel 0?3 dma status undefined ro 0ah 1ah channel 0?3 dma write single mask 000001xxb wo 0bh 1bh channel 0?3 dma channel mode 000000xxb wo 0ch 1ch channel 0?3 dma clear byte pointer undefined wo 0dh 1dh channel 0?3 dma master clear undefined wo 0eh 1eh channel 0?3 dma clear mask undefined wo 0fh 1fh channel 0?3 dma write all mask 0fh r/w 80h 90h reserved page undefined r/w 81h 91h channel 2 dma memory low page undefined r/w 82h ? channel 3 dma memory low page undefined r/w 83h 93h channel 1 dma memory low page undefined r/w 84h?86h 94h?96h reserved pages undefined r/w 87h 97h channel 0 dma memory low page undefined r/w 88h 98h reserved page undefined r/w 89h 99h channel 6 dma memory low page undefined r/w 8ah 9ah channel 7 dma memory low page undefined r/w 8bh 9bh channel 5 dma memory low page undefined r/w 8ch?8eh 9ch?9eh reserved page undefined r/w 8fh 9fh refresh low page undefined r/w c0h c1h channel 4 dma base & current address undefined r/w c2h c3h channel 4 dma base & current count undefined r/w c4h c5h channel 5 dma base & current address undefined r/w c6h c7h channel 5 dma base & current count undefined r/w c8h c9h channel 6 dma base & current address undefined r/w cah cbh channel 6 dma base & current count undefined r/w cch cdh channel 7 dma base & current address undefined r/w http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 412 datasheet 13.2.1 dmabase_ca?dma base and current address registers (lpc i/f?d31:f0) i/o address: ch. #0 = 00h; ch. #1 = 02hattribute:r/w ch. #2 = 04h; ch. #3 = 06hsize:16 bit (per channel), ch. #5 = c4h ch. #6 = c8h but accessed in two 8-bit ch. #7 = cch; quantities default value: undefined lockable: no power well:core ceh cfh channel 7 dma base & current count undefined r/w d0h d1h channel 4?7 dma command undefined wo channel 4?7 dma status undefined ro d4h d5h channel 4?7 dma write single mask 000001xxb wo d6h d7h channel 4?7 dma channel mode 000000xxb wo d8h d9h channel 4?7 dma clear byte pointer undefined wo dah dbh channel 4?7 dma master clear undefined wo dch ddh channel 4?7 dma clear mask undefined wo deh dfh channel 4?7 dma write all mask 0fh r/w table 13-2. dma registers (sheet 2 of 2) port alias register name default type bit description 15:0 base and current address ? r/w. this register determin es the address for the transfers to be performed. the address specif ied points to two sepa rate registers. on writes, the value is stored in the base address register and copied to the current address register. on reads, the value is returned from the current address register. the address increments/decrements in the current address register after each transfer, depending on the mode of the transfer. if the channel is in auto-initialize mode, the current address register will be reloaded from the base address register after a terminal count is generated. for transfers to/from a 16-bit slave (channels 5?7), the address is shifted left one bit location. bit 15 will be shifted into bit 16. the register is accessed in 8 bit quantities. the byte is po inted to by the current byte pointer flip/flop. before acce ssing an address regi ster, the byte pointer flip/flop should be cleared to ensure that th e low byte is accessed first. http://www..net/ datasheet pdf - http://www..net/ datasheet 413 lpc interface bridge registers (d31:f0) 13.2.2 dmabase_cc?dma base an d current count registers (lpc i/f?d31:f0) i/o address: ch. #0 = 01h; ch. #1 = 03hattribute:r/w ch. #2 = 05h; ch. #3 = 07hsize:16-bit (per channel), ch. #5 = c6h; ch. #6 = cah but accessed in two 8-bit ch. #7 = ceh; quantities default value: undefined lockable: no power well:core 13.2.3 dmamem_lp?dma memory low page registers (lpc i/f?d31:f0) i/o address: ch. #0 = 87h; ch. #1 = 83h ch. #2 = 81h; ch. #3 = 82h ch. #5 = 8bh; ch. #6 = 89h ch. #7 = 8ah; attribute:r/w default value: undefined size: 8-bit lockable: no power well:core bit description 15:0 base and current count ? r/w. this register determines the number of transfers to be performed. the address specified points to two separate regist ers. on writes, the value is stored in the base count register and copied to the current count register. on reads, the value is returned from the current count register. the actual number of transfers is one more than the number programmed in the base count register (i.e., programming a count of 4h results in 5 transfers). the count is decrements in the current count register after each transfer. when the value in the register rolls from 0 to ffffh, a terminal count is generated. if the channel is in auto- initialize mode, the current count register will be reloaded from the base count register after a termin al count is generated. for transfers to/from an 8-bit slave (chann els 0?3), the count register indicates the number of bytes to be transferred. for tran sfers to/from a 16-bit slave (channels 5?7), the count register indicates the num ber of words to be transferred. the register is accessed in 8 bit quantities. the byte is po inted to by the current byte pointer flip/flop. before acce ssing a count register, the byte pointer flip/flop should be cleared to ensure that the low byte is accessed first. bit description 7:0 dma low page (isa address bits [23:16]) ? r/w. this register works in conjunction with the dma controller's current address register to define the complete 24-bit address for the dma channel. this register remains static throughout the dma transfer. bit 16 of this register is ignored when in 16 bit i/o count by words mode as it is replaced by the bit 15 shifted out from the current address register. http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 414 datasheet 13.2.4 dmacmd?dma command re gister (lpc i/f?d31:f0) i/o address: ch. #0 ? 3 = 08h; ch. #4 ? 7 = d0h attribute:wo default value: undefined size: 8-bit lockable: no power well:core 13.2.5 dmasta?dma status re gister (lpc i/f?d31:f0) i/o address: ch. #0 ? 3 = 08h; ch. #4 ? 7 = d0h attribute:ro default value: undefined size: 8-bit lockable: no power well:core bit description 7:5 reserved. must be 0. 4 dma group arbitration priority ? wo. each channel group is individually assigned either fixed or rotating arbitration priority. at part reset, each gr oup is initialized in fixed priority. 0 = fixed priority to the channel group 1 = rotating priority to the group. 3 reserved. must be 0. 2 dma channel group enable ? wo. both channel groups are enabled following part reset. 0 = enable the dma channel group. 1 = disable. disabling channel group 4?7 also disables channel gr oup 0?3, which is cascaded through channel 4. 1:0 reserved. must be 0. bit description 7:4 channel request status ? ro. when a valid dma reques t is pending for a channel, the corresponding bit is set to 1. when a dma request is not pending for a particular channel, the corresponding bit is set to 0. the source of the dreq may be hardware or a software request. note that channel 4 is the cascade ch annel, so the request status of channel 4 is a logical or of the requ est status for chan nels 0 through 3. 4 = channel 0 5 = channel 1 (5) 6 = channel 2 (6) 7 = channel 3 (7) 3:0 channel terminal count status ? ro. when a channel reaches terminal count (tc), its status bit is set to 1. if tc has not been reached, the status bit is set to 0. channel 4 is programmed for cascade, so the tc bi t response for channe l 4 is irrelevant. 0 = channel 0 1 = channel 1 (5) 2 = channel 2 (6) 3 = channel 3 (7) http://www..net/ datasheet pdf - http://www..net/ datasheet 415 lpc interface bridge registers (d31:f0) 13.2.6 dma_wrsmsk?dma write single mask register (lpc i/f?d31:f0) i/o address: ch. #0 ? 3 = 0ah; ch. #4 ? 7 = d4h attribute:wo default value: 0000 01xx size: 8-bit lockable: no power well:core bit description 7:3 reserved. must be 0. 2 channel mask select ? wo. 0 = enable dreq for the selected channel. the channel is selected through bits [1:0]. therefore, only one channel can be masked / unmasked at a time. 1 = disable dreq for the selected channel. 1:0 dma channel select ? wo. these bits select the dma channel mode register to program. 00 = channel 0 (4) 01 = channel 1 (5) 10 = channel 2 (6) 11 = channel 3 (7) http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 416 datasheet 13.2.7 dmach_mode?dma ch annel mode register (lpc i/f?d31:f0) i/o address: ch. #0 ? 3 = 0bh; ch. #4 ? 7 = d6h attribute:wo default value: 0000 00xx size: 8-bit lockable: no power well:core bit description 7:6 dma transfer mode ? wo. each dma channel can be programmed in one of four different modes: 00 = demand mode 01 = single mode 10 = reserved 11 = cascade mode 5 address increment/decrement select ? wo. this bit controls address increment/ decrement during dma transfers. 0 = address increment. (default af ter part reset or master clear) 1 = address decrement. 4 autoinitialize enable ? wo. 0 = autoinitialize feature is di sabled and dma transfers term inate on a terminal count. a part reset or master clea r disables autoinitialization. 1 = dma restores the base address and co unt registers to th e current registers following a terminal count (tc). 3:2 dma transfer type ? wo. these bits represent the direction of the dma transfer. when the channel is programmed for cascade mode, (bits[7:6] = 11) the transfer type is irrelevant. 00 = verify ? no i/o or memory strobes generated 01 = write ? data transferred from the i/o devices to memory 10 = read ? data transferred from memory to the i/o device 11 = invalid 1:0 dma channel select ? wo. these bits select the dma ch annel mode register that will be written by bits [7:2]. 00 = channel 0 (4) 01 = channel 1 (5) 10 = channel 2 (6) 11 = channel 3 (7) http://www..net/ datasheet pdf - http://www..net/ datasheet 417 lpc interface bridge registers (d31:f0) 13.2.8 dma clear byte pointer register (lpc i/f?d31:f0) i/o address: ch. #0 ? 3 = 0ch; ch. #4 ? 7 = d8h attribute:wo default value: xxxx xxxx size: 8-bit lockable: no power well:core 13.2.9 dma master clear re gister (lpc i/f?d31:f0) i/o address: ch. #0 ? 3 = 0dh; ch. #4 ? 7 = dah attribute:wo default value: xxxx xxxx size: 8-bit 13.2.10 dma_clmsk?dma clear mask register (lpc i/f?d31:f0) i/o address: ch. #0 ? 3 = 0eh; ch. #4 ? 7 = dch attribute:wo default value: xxxx xxxx size: 8-bit lockable: no power well:core bit description 7:0 clear byte pointer ? wo. no specific pattern. comm and enabled with a write to the i/o port address. writing to th is register initializes the byte pointer flip/flop to a known state. it clears the internal latch used to address the uppe r or lower byte of the 16-bit address and word count registers. the latch is also cleared by part reset and by the master clear command. this command prec edes the first acce ss to a 16-bit dma controller register. the first access to a 16-bit register will then access the significant byte, and the second access automatically accesses the most significant byte. bit description 7:0 master clear ? wo. no specific pattern. enabled wi th a write to the port. this has the same effect as the hardware reset. the command, status , request, and byte pointer flip/flop registers are cleared and the mask register is set. bit description 7:0 clear mask register ? wo. no specific pattern. command enabled with a write to the port. http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 418 datasheet 13.2.11 dma_wrmsk?dma writ e all mask register (lpc i/f?d31:f0) i/o address: ch. #0 ? 3 = 0fh; ch. #4 ? 7 = deh attribute:r/w default value: 0000 1111 size: 8-bit lockable: no power well:core bit description 7:4 reserved. must be 0. 3:0 channel mask bits ? r/w. this register permits all four channels to be simultaneously enabled/disabled instea d of enabling/disabling each channel individually, as is the case with the mask re gister ? write single mask bit. in addition, this register has a read path to allow the status of the channel mask bits to be read. a channel's mask bit is automatically set to 1 when the current byte/word count register reaches terminal count (unless the channel is in auto-initialization mode). setting the bit(s) to a 1 disa bles the corresponding dreq(s). setting the bit(s) to a 0 enables the corresponding dreq(s). bits [3:0] are set to 1 upon part reset or master clear. when read, bits [3:0] indicate the dma channel [3:0] ([7:4]) mask status. bit 0 = channel 0 (4)1 = masked, 0 = not masked bit 1 = channel 1 (5)1 = masked, 0 = not masked bit 2 = channel 2 (6)1 = masked, 0 = not masked bit 3 = channel 3 (7)1 = masked, 0 = not masked note: disabling channel 4 also disables channe ls 0?3 due to the cascade of channels 0?3 through channel 4. http://www..net/ datasheet pdf - http://www..net/ datasheet 419 lpc interface bridge registers (d31:f0) 13.3 timer i/o registers (lpc i/f?d31:f0) port aliases register name default value type 40h 50h counter 0 interval time status byte format 0xxxxxxxb ro counter 0 counter acce ss port undefined r/w 41h 51h counter 1 interval time status byte format 0xxxxxxxb ro counter 1 counter acce ss port undefined r/w 42h 52h counter 2 interval time status byte format 0xxxxxxxb ro counter 2 counter acce ss port undefined r/w 43h 53h timer control word undefined wo timer control word register xxxxxxx0b wo counter latch command x0h wo http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 420 datasheet 13.3.1 tcw?timer control word register (lpc i/f?d31:f0) i/o address: 43h attribute: wo default value: all bits undefined size: 8 bits this register is programmed prior to any counter being accessed to specify counter modes. following part reset, the control word s for each register are undefined and each counter output is 0. each timer must be programmed to bring it into a known state. there are two special commands that can be issued to the counters through this register, the read back command and the counter latch command. when these commands are chosen, several bits within this register are redefined. these register formats are described as follows: bit description 7:6 counter select ? wo. the counter selection bits select the counter the control word acts upon as shown below. the read back command is selected when bits[7:6] are both 1. 00 = counter 0 select 01 = counter 1 select 10 = counter 2 select 11 = read back command 5:4 read/write select ? wo. these bits are the read/w rite control bits. the actual counter programming is done through the co unter port (40h for counter 0, 41h for counter 1, and 42h for counter 2). 00 = counter latch command 01 = read/write least significant byte (lsb) 10 = read/write most significant byte (msb) 11 = read/write lsb then msb 3:1 counter mode selection ? wo. these bits select one of six possible modes of operation for the selected counter. 0 binary/bcd countdown select ? wo. 0 = binary countdown is used. the largest possible binary count is 2 16 1 = binary coded decimal (bcd ) count is used. the largest possible bcd count is 10 4 bit value mode 000b mode 0 out signal on end of count (=0) 001b mode 1 hardware retriggerable one- shot x10b mode 2 rate generator (divide by n counter) x11b mode 3 square wave output 100b mode 4 software triggered strobe 101b mode 5 hardware triggered strobe http://www..net/ datasheet pdf - http://www..net/ datasheet 421 lpc interface bridge registers (d31:f0) rdbk_cmd?read back comma nd (lpc i/f?d31:f0) the read back command is used to determine the count value, programmed mode, and current states of the out pin and null count flag of the selected counter or counters. status and/or count may be latched in any or all of the counters by selecting the counter during the register write. the count and status remain latched until read, and further latch commands are ignored until the count is read. both count and status of the selected counters may be latched simultaneously by setting both bit 5 and bit 4 to 0. if both are latched, the first read op eration from that counter returns the latched status. the next one or two reads, depend ing on whether the counter is programmed for one or two byte counts, returns the latched count. subsequent reads return an unlatched count. ltch_cmd?counter latch co mmand (lpc i/f?d31:f0) the counter latch command latches the current count value. this command is used to insure that the count read from the counter is accurate. the count value is then read from each counter's count register through the counter ports access ports register (40h for counter 0, 41h for counter 1, and 42h for counter 2). the count must be read according to the programmed format, i.e., if the counter is programmed for two byte counts, two bytes must be read. the two byte s do not have to be read one right after the other (read, write, or programming operations for other counters may be inserted between the reads). if a counter is latche d once and then latc hed again before the count is read, the second counter latch command is ignored. bit description 7:6 read back command. must be 11 to select the read back command 5 latch count of se lected counters . 0 = current count value of the sele cted counters will be latched 1 = current count will not be latched 4 latch status of selected counters . 0 = status of the selected counters will be latched 1 = status will not be latched 3 counter 2 select . 1 = counter 2 count and/or status will be latched 2 counter 1 select . 1 = counter 1 count and/or status will be latched 1 counter 0 select . 1 = counter 0 count and/or status will be latched. 0 reserved. must be 0. bit description 7:6 counter selection. these bits select the counter for la tching. if ?11? is written, then the write is interpreted as a read back command. 00 = counter 0 01 = counter 1 10 = counter 2 5:4 counter latch command . 00 = selects the co unter latch command. 3:0 reserved. must be 0. http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 422 datasheet 13.3.2 sbyte_fmt?interval timer status byte format register (lpc i/f?d31:f0) i/o address: counter 0 = 40h, counter 1 = 41h, attribute: ro counter 2 = 42h size: 8 bits per counter default value: bits[6:0] undefined, bit 7=0 each counter's status byte can be read following a read back command. if latch status is chosen (bit 4=0, read back command) as a read back option for a given counter, the next read from the counter's counter access ports register (40h for counter 0, 41h for counter 1, and 42h for counter 2) returns th e status byte. the status byte returns the following: bit description 7 counter out pin state ? ro. 0 = out pin of the counter is also a 0 1 = out pin of the counter is also a 1 6 count register status ? ro. this bit indicates when the last count written to the count register (cr) has been loaded into the counting element (ce). the exact time this happens depends on the counter mode, but until the count is loaded into the counting element (ce), the count value will be incorrect. 0 = count has been transf erred from cr to ce and is available for reading. 1 = null count. count has not been transferre d from cr to ce and is not yet available for reading. 5:4 read/write selection status ? ro. these reflect the re ad/write selection made through bits[5:4] of the control register. th e binary codes returned during the status read match the codes used to progra m the counter read /write selection. 00 = counter latch command 01 = read/write least significant byte (lsb) 10 = read/write most significant byte (msb) 11 = read/write lsb then msb 3:1 mode selection status ? ro. these bits return the counter mode programming. the binary code returned matche s the code used to program the counter mode, as listed under the bit function above. 000 = mode 0 ? out signal on end of count (=0) 001 = mode 1 ? hardware retriggerable one-shot x10 = mode 2 ? rate generator (divide by n counter) x11 = mode 3 ? square wave output 100 = mode 4 ? software triggered strobe 101 = mode 5 ? hardware triggered strobe 0 countdown type status ? ro. this bit reflects the current countdown type. 0 = binary countdown 1 = binary coded decimal (bcd) countdown. http://www..net/ datasheet pdf - http://www..net/ datasheet 423 lpc interface bridge registers (d31:f0) 13.3.3 counter access ports register (lpc i/f?d31:f0) i/o address: counter 0 ? 40h, counter 1 ? 41h, attribute: r/w counter 2 ? 42h default value: all bits undefined size: 8 bit bit description 7:0 counter port ? r/w. each counter po rt address is used to program the 16-bit count register. the order of progra mming, either lsb only, msb only, or lsb then msb, is defined with the interval counter control register at port 43 h. the counter port is also used to read the current co unt from the count register, an d return the status of the counter programming following a read back command. http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 424 datasheet 13.4 8259 interrupt controller (pic) registers (lpc i/f?d31:f0) 13.4.1 interrupt controller i/o map (lpc i/f?d31:f0) the interrupt controller registers are located at 20h and 21h for the master controller (irq 0?7), and at a0h and a1h for the slave controller (irq 8?13). these registers have multiple functions, depending upon the data written to them. ta b l e 1 3 - 3 shows the different register possibilities for each address. note: refer to note addressing active-low interrupt sources in 8259 interrupt controllers section ( section 5.8 ). table 13-3. pic registers (lpc i/f?d31:f0) port aliases register name default value type 20h 24h, 28h, 2ch, 30h, 34h, 38h, 3ch master pic icw1 init. cmd word 1 undefined wo master pic ocw2 op ctrl word 2 001xxxxxb wo master pic ocw3 op ctrl word 3 x01xxx10b wo 21h 25h, 29h, 2dh, 31h, 35h, 39h, 3dh master pic icw2 init. cmd word 2 undefined wo master pic icw3 init. cmd word 3 undefined wo master pic icw4 init. cmd word 4 01h wo master pic ocw1 op ctrl word 1 00h r/w a0h a4h, a8h, ach, b0h, b4h, b8h, bch slave pic icw1 init. cmd word 1 undefined wo slave pic ocw2 op ctrl word 2 001xxxxxb wo slave pic ocw3 op ctrl word 3 x01xxx10b wo a1h a5h, a9h, adh, b1h, b5h, b9h, bdh slave pic icw2 init. cmd word 2 undefined wo slave pic icw3 init. cmd word 3 undefined wo slave pic icw4 init. cmd word 4 01h wo slave pic ocw1 op ctrl word 1 00h r/w 4d0h ? master pic edge/level triggered 00h r/w 4d1h ? slave pic edge/level triggered 00h r/w http://www..net/ datasheet pdf - http://www..net/ datasheet 425 lpc interface bridge registers (d31:f0) 13.4.2 icw1?initialization command word 1 register (lpc i/f?d31:f0) offset address: master controller ? 20h attribute: wo slave controller ? a0h size: 8 bit /controller default value: all bits undefined a write to initialization command word 1 starts the interrupt controller initialization sequence, during which the following occurs: 1. the interrupt mask register is cleared. 2. irq7 input is assigned priority 7. 3. the slave mode address is set to 7. 4. special mask mode is cleared and status read is set to irr. once this write occurs, the controller expects writes to icw2, icw3, and icw4 to complete the initialization sequence. bit description 7:5 icw/ocw select ? wo. these bits are mcs-85 specific, and not needed. 000 = should be programmed to ?000? 4 icw/ocw select ? wo. 1 = this bit must be a 1 to select icw1 and enable the icw2, icw3, and icw4 sequence. 3 edge/level bank select (ltim) ? wo. disabled. replac ed by the edge/level triggered control registers (elc r, d31:f0:4d0h, d31:f0:4d1h). 2 adi ? wo. 0 = ignored for the ich10. should be programmed to 0. 1 single or cascade (sngl) ? wo. 0 = must be programmed to a 0 to indicate two controllers operating in cascade mode. 0 icw4 write required (ic4) ? wo. 1 = this bit must be programmed to a 1 to indicate that icw4 needs to be programmed. http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 426 datasheet 13.4.3 icw2?initialization command word 2 register (lpc i/f?d31:f0) offset address: master controller ? 21h attribute: wo slave controller ? a1h size: 8 bit /controller default value: all bits undefined icw2 is used to initialize the interrupt contro ller with the five most significant bits of the interrupt vector address. the value programmed for bits[7:3] is used by the processor to define the base address in the interrupt vector table for the interrupt routines associated with each irq on the controller. typical isa icw2 values are 08h for the master controller and 70h for the slave controller. bit description 7:3 interrupt vector base address ? wo. bits [7:3] define the base address in the interrupt vector table for the interrupt routines as sociated with each interrupt request level input. 2:0 interrupt request level ? wo. when writing icw2, these bits should all be 0. during an interrupt acknowledge cycle, these bits are programmed by the interrupt controller with the interrupt to be serviced. this is combined with bits [7:3] to form the interrupt vector driven onto the data bus during the second inta# cycle. the code is a three bit binary code: code master interrupt slave interrupt 000b irq0 irq8 001b irq1 irq9 010b irq2 irq10 011b irq3 irq11 100b irq4 irq12 101b irq5 irq13 110b irq6 irq14 111b irq7 irq15 http://www..net/ datasheet pdf - http://www..net/ datasheet 427 lpc interface bridge registers (d31:f0) 13.4.4 icw3?master controller initialization command word 3 register (lpc i/f?d31:f0) offset address: 21h attribute: wo default value: all bits undefined size: 8 bits 13.4.5 icw3?slave controller initialization command word 3 register (lpc i/f?d31:f0) offset address: a1h attribute: wo default value: all bits undefined size: 8 bits bit description 7:3 0 = these bits must be programmed to 0. 2 cascaded interrupt controller irq connection ? wo. this bit indicates that the slave controller is cascaded on irq2. when irq8#?irq15 is asserted, it goes through the slave controller?s priority resolver. the slave controller?s intr output onto irq2. irq2 then goes through the master controller ?s priority solver. if it wins, the intr signal is asserted to the processor, and th e returning interrupt ac knowledge returns the interrupt vector for the slave controller. 1 = this bit must always be programmed to a 1. 1:0 0 = these bits must be programmed to 0. bit description 7:3 0 = these bits must be programmed to 0. 2:0 slave identification code ? wo. these bits are compared against the slave identification code broadcast by the master co ntroller from the trailing edge of the first internal inta# pulse to the trailing edge of the second internal inta# pulse. these bits must be programmed to 02h to match the co de broadcast by the master controller. when 02h is broadcast by the master contro ller during the inta# sequence, the slave controller assumes responsibility for broadcasting the interrupt vector. http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 428 datasheet 13.4.6 icw4?initialization command word 4 register (lpc i/f?d31:f0) offset address: master controller ? 021h attribute:wo slave controller ? 0a1h size: 8 bits default value: 01h 13.4.7 ocw1?operational contro l word 1 (interrupt mask) register (lpc i/f?d31:f0) offset address: master controller ? 021h attribute:r/w slave controller ? 0a1h size: 8 bits default value: 00h bit description 7:5 0 = these bits must be programmed to 0. 4 special fully nested mode (sfnm) ? wo. 0 = should normally be disabled by writing a 0 to this bit. 1 = special fully nested mode is programmed. 3 buffered mode (buf) ? wo. 0 = must be programmed to 0 for the ich10. this is non-buffered mode. 2 master/slave in buffered mode ? wo. not used. 0 = should always be programmed to 0. 1 automatic end of interrupt (aeoi) ? wo. 0 = this bit should normally be programmed to 0. this is the norm al end of interrupt. 1 = automatic end of interrupt (aeoi) mode is programmed. 0 microprocessor mode ? wo. 1 = must be programmed to 1 to indicate that the controller is operating in an intel architecture-based system. bit description 7:0 interrupt request mask ? r/w. when a 1 is written to any bit in this register, the corresponding irq line is masked. when a 0 is written to any bit in this register, the corresponding irq mask bit is cleared, and in terrupt requests will again be accepted by the controller. masking irq2 on the master controller will also mask the interrupt requests from the slave controller. http://www..net/ datasheet pdf - http://www..net/ datasheet 429 lpc interface bridge registers (d31:f0) 13.4.8 ocw2?operational co ntrol word 2 register (lpc i/f?d31:f0) offset address: master controller ? 020h attribute:wo slave controller ? 0a0h size: 8 bits default value: bit[4:0]=undefined, bit[7:5]=001 following a part reset or icw initialization, the controller enters the fully nested mode of operation. non-specific eoi without rotati on is the default. both rotation mode and specific eoi mode are disabl ed following initialization. bit description 7:5 rotate and eoi codes (r, sl, eoi) ? wo. these three bits control the rotate and end of interrupt modes and combinations of the two. 000 = rotate in auto eoi mode (clear) 001 = non-specific eoi command 010 = no operation 011 = *specific eoi command 100 = rotate in auto eoi mode (set) 101 = rotate on non-specific eoi command 110 = *set priority command 111 = *rotate on specific eoi command *l0 ? l2 are used 4:3 ocw2 select ? wo. when selecting ocw2, bits 4:3 = ?00? 2:0 interrupt level select (l2, l1, l0) ? wo. l2, l1, and l0 determine the interrupt level acted upon when the sl bit is active. a simple binary code, outlined below, selects the channel for the command to act upon. when the sl bit is inactive, these bits do not have a defined function; programming l2, l1 and l0 to 0 is sufficient in this case. code interrupt level code interrupt level 000b irq0/8 000b irq4/12 001b irq1/9 001b irq5/13 010b irq2/10 010b irq6/14 011b irq3/11 011b irq7/15 http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 430 datasheet 13.4.9 ocw3?operational control word 3 register (lpc i/f?d31:f0) offset address: master controller ? 020h attribute:wo slave controller ? 0a0h size: 8 bits default value: bit[6,0]=0, bit[7,4:2]=undefined, bit[5,1]=1 bit description 7 reserved. must be 0. 6 special mask mode (smm) ? wo. 1 = the special mask mode can be used by an interrupt service routine to dynamically alter the system priority structure while th e routine is executing, through selective enabling/disabling of the other channel's ma sk bits. bit 5, the esmm bit, must be set for this bit to have any meaning. 5 enable special mask mode (esmm) ? wo. 0 = disable. the smm bit becomes a ?don't care?. 1 = enable the smm bit to set or reset the special mask mode. 4:3 ocw3 select ? wo. when selecting ocw3, bits 4:3 = 01 2 poll mode command ? wo. 0 = disable. poll command is not issued. 1 = enable. the next i/o read to the interr upt controller is treated as an interrupt acknowledge cycle. an encode d byte is driven onto the data bus, repr esenting the highest priority level requesting service. 1:0 register read command ? wo. these bits provide control for reading the in-service register (isr) and the interrupt request register (irr). when bit 1=0, bit 0 will not affect the register read sele ction. when bit 1=1, bit 0 selects the register status returned following an ocw3 read. if bit 0=0, the irr will be read . if bit 0=1, the isr will be read. following icw initialization, th e default ocw3 port address read will be ?read irr?. to retain the curre nt selection (read isr or read irr), always write a 0 to bit 1 when programming this register. the selected regist er can be read repeatedly without reprogramming ocw3. to select a new status regist er, ocw3 must be reprogrammed prior to attempting the read. 00 = no action 01 = no action 10 = read irq register 11 = read is register http://www..net/ datasheet pdf - http://www..net/ datasheet 431 lpc interface bridge registers (d31:f0) 13.4.10 elcr1?master controller edge/level triggered register (lpc i/f?d31:f0) offset address: 4d0h attribute: r/w default value: 00h size: 8 bits in edge mode, (bit[x] = 0), the interrupt is recognized by a low to high transition. in level mode (bit[x] = 1), the interrupt is recognized by a high level. the cascade channel, irq2, the heart beat timer (irq0), and the keyboard controller (irq1), cannot be put into level mode. bit description 7 irq7 ecl ? r/w. 0 = edge. 1 = level. 6 irq6 ecl ? r/w. 0 = edge. 1 = level. 5 irq5 ecl ? r/w. 0 = edge. 1 = level. 4 irq4 ecl ? r/w. 0 = edge. 1 = level. 3 irq3 ecl ? r/w. 0 = edge. 1 = level. 2:0 reserved. must be 0. http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 432 datasheet 13.4.11 elcr2?slave controller edge/level triggered register (lpc i/f?d31:f0) offset address: 4d1h attribute: r/w default value: 00h size: 8 bits in edge mode, (bit[x] = 0), the interrupt is recognized by a low to high transition. in level mode (bit[x] = 1), the interrupt is recogn ized by a high level. the real time clock, irq8#, and the floating point error interrup t, irq13, cannot be programmed for level mode. bit description 7 irq15 ecl ? r/w. 0 = edge 1 = level 6 irq14 ecl ? r/w. 0 = edge 1 = level 5 reserved. must be 0. 4 irq12 ecl ? r/w. 0 = edge 1 = level 3 irq11 ecl ? r/w. 0 = edge 1 = level 2 irq10 ecl ? r/w. 0 = edge 1 = level 1 irq9 ecl ? r/w. 0 = edge 1 = level 0 reserved. must be 0. http://www..net/ datasheet pdf - http://www..net/ datasheet 433 lpc interface bridge registers (d31:f0) 13.5 advanced programmable interrupt controller (apic)(d31:f0) 13.5.1 apic register ma p (lpc i/f?d31:f0) the apic is accessed via an indirect addressing scheme. two registers are visible by software for manipulation of most of the apic registers. these registers are mapped into memory space. the address bits 15 :12 (consumer only) and 19:12 (corporate only) of the address range are programmab le through bits 7:4 (consumer only) and 7:0 (corporate only) of oic register (chipset config registers:offset 31ffh for consumer family and offset 31feh for corporate family) the registers are shown in table 13-4 . table 13-5 lists the registers which can be accessed within the apic via the index register. when accessing these registers, accesses must be done one dword at a time. for example, software should never access byte 2 from the data register before accessing bytes 0 and 1. the hardware will not attempt to recover from a bad programming model in this case. table 13-4. apic direct registers (lpc i/f?d31:f0) address mnemonic register name size type fec_ _0000h (corporate only) ind index 8 bits r/w fec0_0000h (consumer only) ind index 8 bits r/w fec_ _0010h (corporate only) dat data 32 bits r/w fec0_0010h (consumer only) dat data 32 bits r/w fec_ _0040h (corporate only) eoir eoi 32 bits wo feco_0040h (consumer only) eoir eoi 32 bits wo table 13-5. apic indirect registers (lpc i/f?d31:f0) index mnemonic register name size type 00 id identification 32 bits r/w 01 ver version 32 bits ro 02?0f ? reserved ? ro 10?11 redir_tbl0 redirection table 0 64 bits r/w, ro 12?13 redir_tbl1 redirection table 1 64 bits r/w, ro ... ... ... ... ... 3e?3f redir_tbl23 redirection table 23 64 bits r/w, ro 40?ff ? reserved ? ro http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 434 datasheet 13.5.2 ind?index regist er (lpc i/f?d31:f0) memory address fec0_0000h (c onsumer only) attribute: r/w fec _ _ 0000h (corporate only) default value: 00h size: 8 bits the index register will select which apic indirect register to be manipulated by software. the selector values for the indirect registers are listed in ta b l e 1 3 - 5 . software will program this register to select the desired apic internal register . 13.5.3 dat?data register (lpc i/f?d31:f0) memory address fec0_0000h (consumer only) attribute: r/w fec _ _ 0000h (corporate only) default value: 00000000h size: 32 bits this is a 32-bit register specifying the data to be read or written to the register pointed to by the index register. this register can only be accessed in dword quantities. bit description 7:0 apic index ? r/w. this is an 8-bit pointer into the i/o apic register table. bit description 7:0 apic data ? r/w. this is a 32-bit register for the da ta to be read or written to the apic indirect register ( figure 13-5 ) pointed to by the index register (memory address fec0_0000h). http://www..net/ datasheet pdf - http://www..net/ datasheet 435 lpc interface bridge registers (d31:f0) 13.5.4 eoir?eoi register (lpc i/f?d31:f0) memory address fec0_0000h (consumer only) attribute: r/w fec _ _ 0000h (corporate only) default value: n/a size: 32 bits the eoi register is present to provide a mechanism to maintain the level triggered semantics for level-triggered interrupts issued on the parallel bus. when a write is issued to this register, th e i/o apic will check the lower 8 bits written to this register, and compare it with the vector field for each entry in the i/o redirection table. when a match is found, the remote_irr bit (index offset 10h, bit 14) for that i/o redirection entry will be cleared. note: if multiple i/o redirection entries, for any reason, assign the same vector for more than one interrupt input, each of those entr ies will have the remote_irr bit reset to 0. the interrupt which was prematurely reset will not be lost because if its input remained active when the remote_irr bit is cleared, the interrupt will be reissued and serviced at a later time. note: only bits 7:0 are ac tually used. bits 31:8 are ignored by the ich10. note: to provide for future expansion, the processo r should always write a value of 0 to bits 31:8. bit description 31:8 reserved. to provide for future expansion, th e processor should always write a value of 0 to bits 31:8. 7:0 redirection entry clear ? wo. when a write is issued to this register, the i/o apic will check this field, and compare it with the vector field for each entry in the i/o redirection table. when a match is found, th e remote_irr bit for that i/o redirection entry will be cleared. http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 436 datasheet 13.5.5 id?identification re gister (lpc i/f?d31:f0) index offset: 00h attribute: r/w default value: 00000000h size: 32 bits the apic id serves as a physical name of the apic. the apic bus arbitration id for the apic is derived from its i/o apic id. this register is reset to 0 on power-up reset. 13.5.6 ver?version regist er (lpc i/f?d31:f0) index offset: 01h attribute: ro, rwo default value: 00170020h size: 32 bits each i/o apic contains a hardwired version register that identifies different implementation of apic and their versions . the maximum redirection entry information also is in this register, to let software kn ow how many interrupt are supported by this apic. bit description 31:28 reserved 27:24 apic id ? r/w. software must program th is value before using the apic. 23:16 reserved 15 scratchpad bit. 14:0 reserved bit description 31:24 reserved 23:16 maximum redirection entries (mre) ? rwo. this is the entry number (0 being the lowest entry) of the highest entry in the redirection table. it is equal to the number of interrupt input pins mi nus one and is in the range 0 through 239. in the ich10 this field is hardwired to 17h to indicate 24 interrupts. bios must write to this field after pltrst# to lockdown the value. this allows bios to utilize some of the entries for its own pu rpose and thus advertising fewer ioxapic redirection entries to the os. 15 pin assertion register supported (prq) ? ro. indicate that the ioxapic does not implement the pin assertion register. 14:8 reserved 7:0 version (vs) ? ro. this is a version number that identifies the implementation version. http://www..net/ datasheet pdf - http://www..net/ datasheet 437 lpc interface bridge registers (d31:f0) 13.5.7 redir_tbl?redirection table (lpc i/f?d31:f0) index offset: 10h ? 11h (vector 0) throughattribute: r/w, ro 3e ? 3fh (vector 23) default value: bit 16 = 1. all other bits undefinedsize:64 bits each, (accessed as two 32 bit quantities) the redirection table has a dedicated entry for each interrupt input pin. the information in the redirection table is used to translate the interrupt manifestation on the corresponding interrupt pin into an apic message. the apic will respond to an edge triggered in terrupt as long as the interrupt is held until after the acknowledge cycle has begun. once the interrupt is detected, a delivery status bit internally to the i/o apic is se t. the state machine will step ahead and wait for an acknowledgment from the apic unit th at the interrupt message was sent. only then will the i/o apic be able to recognize a new edge on that interrupt pin. that new edge will only result in a new invocation of the handler if its acceptance by the destination apic causes the interrupt request register bit to go from 0 to 1. (in other words, if the interrupt was not already pending at the destination.) bit description 63:56 destination ? r/w. if bit 11 of this entry is 0 (physical), then bits 59:56 specifies an apic id. in this case, bits 63:59 shou ld be programmed by software to 0. if bit 11 of this entry is 1 (logical), then bits 63:56 specify the logical destination address of a set of processors. 55:48 extended destination id (edid) ? ro. these bits are sent to a local apic only when in processor system bus mode. th ey become bits 11:4 of the address. 47:17 reserved 16 mask ? r/w. 0 = not masked: an edge or level on this in terrupt pin results in the delivery of the interrupt to the destination. 1 = masked: interrupts are not delivered nor held pending. setting this bit after the interrupt is accepted by a local apic has no effect on that inte rrupt. this behavior is identical to the device withdrawing th e interrupt before it is posted to the processor. it is software's responsibility to deal with the case where the mask bit is set after the interrupt message has been ac cepted by a local apic unit but before the interrupt is dispen sed to the processor. 15 trigger mode ? r/w. this field indicates the type of signal on the interrupt pin that triggers an interrupt. 0 = edge triggered. 1 = level triggered. 14 remote irr ? r/w. this bit is used for level triggered interrupts; its meaning is undefined for edge tr iggered interrupts. 0 = reset when an eoi message is received from a local apic. 1 = set when local apic/s accept the level interrupt sent by the i/o apic. 13 interrupt input pin polarity ? r/w. this bit specifies the polarity of each interrupt signal connected to the interrupt pins. 0 = active high. 1 = active low. 12 delivery status ? ro. this field contains the current st atus of the delivery of this interrupt. writes to th is bit have no effect. 0 = idle. no activity for this interrupt. 1 = pending. interrupt has been inject ed, but delivery is not complete. http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 438 datasheet note: delivery mode encoding: 000 = fixed. deliver the signal on the intr signal of all processor cores listed in the destination. trigger mode can be edge or level. 001 = lowest priority. deliver the signal on th e intr signal of the processor core that is executing at the lowest priority among all the pr ocessors listed in the specified destination. trigger mode can be edge or level. 010 = smi (system management interrupt). requir es the interrupt to be programmed as edge triggered. the vector informat ion is ignored but must be pr ogrammed to all 0s for future compatibility: not supported 011 = reserved 100 = nmi. deliver the signal on the nmi signal of all processor cores listed in the destination. vector information is ignored. nmi is treated as an edge triggered inte rrupt even if it is programmed as level triggered. for proper oper ation this redirection table entry must be programmed to edge triggered. the nmi delivery mode does not set the rirr bit. if the redirection table is incorrectly set to level, the loop count will co ntinue counting through the redirection table addresses. once the co unt for the nmi pin is reached again, the interrupt will be sent again: not supported 101 = init. deliver the signal to all processor core s listed in the destination by asserting the init signal. all addressed local apics will assume thei r init state. init is always treated as an edge triggered interrupt even if programmed as level triggered. for proper operation this redirection table entry must be programmed to edge triggered. the init delivery mode does not set the rirr bit. if the redirection table is incorrectly set to level, the loop count will continue counting through the redirection table addresses. once the count for the init pin is reached again, the inte rrupt will be sent again: not supported 110 = reserved 111 = extint. deliver the signal to the intr signal of all processor cores listed in the destination as an interrupt that originated in an exte rnally connected 8259a compatible interrupt controller. the inta cycle that corresponds to this extint delivery will be routed to the external controller that is expected to supply the vector. requires the interrupt to be programmed as edge triggered. 11 destination mode ? r/w. this field dete rmines the interpretati on of the destination field. 0 = physical. destination apic id is identified by bits 59:56. 1 = logical. destinations are identified by matching bit 63:56 with the logical destination in the destination format regi ster and logical destination register in each local apic. 10:8 delivery mode ? r/w. this field specifies how the apics listed in the destination field should act upon reception of this signal. certain delivery modes will only operate as intended when used in conjunction with a specific trigger mode. these encodings are listed in the note below: 7:0 vector ? r/w. this field contains the interrupt vector for this interrupt. values range between 10h and feh. bit description http://www..net/ datasheet pdf - http://www..net/ datasheet 439 lpc interface bridge registers (d31:f0) 13.6 real time clock registers 13.6.1 i/o register address map the rtc internal registers and ram are or ganized as two banks of 128 bytes each, called the standard and extended banks. the first 14 bytes of the standard bank contain the rtc time and date information along with four registers, a?d, that are used for configuration of the rtc. the extended bank contains a full 128 bytes of battery backed sram, and will be accessible even when the rtc module is disabled (via the rtc configuration register). registers a?d do not physically exist in the ram. all data movement between the host processor and the real-time clock is done through registers mapped to the standard i/o space. the register map appears in ta b l e 1 3 - 6 . notes: 1. i/o locations 70h and 71h are the standard legacy location for the real-time clock. the map for this bank is shown in ta b l e 1 3 - 7 . locations 72h and 73h are for accessing the extended ram. the extended ram bank is also accessed using an indexed scheme. i/o address 72h is used as the address pointer and i/o address 73h is used as the data register. index addresses above 127h are not valid. if the extended ram is not needed, it may be disabled. 2. software must preserve the value of bit 7 at i/o addresses 70h and 74h. when writing to this address, software must firs t read the value, and then write the same value for bit 7 during the sequential address write. note that port 70h is not directly readable. the only way to read this register is through alt access mode. although rtc index bits 6:0 are readable fr om port 74h, bit 7 will always return 0. if the nmi# enable is not changed during normal operation, software can alternatively read this bit once and then retain the value for all subsequent writes to port 70h. table 13-6. rtc i/o registers i/o locations if u128e bit = 0 function 70h and 74h also alias to 72h and 76h real- time clock (standard ram) index register 71h and 75h also alias to 73h and 77h real-time clock (standard ram) target register 72h and 76h extended ram index register (if enabled) 73h and 77h extended ram targ et register (if enabled) http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 440 datasheet 13.6.2 indexed registers the rtc contains two sets of indexed registers that are accessed using the two separate index and target registers (70/71h or 72/73h), as shown in table 13-7 . table 13-7. rtc (standard) ram bank index name 00h seconds 01h seconds alarm 02h minutes 03h minutes alarm 04h hours 05h hours alarm 06h day of week 07h day of month 08h month 09h year 0ah register a 0bh register b 0ch register c 0dh register d 0eh?7fh 114 bytes of user ram http://www..net/ datasheet pdf - http://www..net/ datasheet 441 lpc interface bridge registers (d31:f0) 13.6.2.1 rtc_rega?register a rtc index: 0a attribute: r/w default value: undefined size: 8-bit lockable: no power well: rtc this register is used for general configuratio n of the rtc functions. none of the bits are affected by rsmrst# or any other ich10 reset signal. bit description 7 update in progress (uip) ? r/w. this bit may be monito red as a status flag. 0 = the update cycle will not start for at least 488 s. the time, calendar, and alarm information in ram is always av ailable when the uip bit is 0. 1 = the update is soon to occur or is in progress. 6:4 division chain select (dv[2:0]) ? r/w. these three bits cont rol the divider chain for the oscillator, and are not affected by rsmrst# or any other reset signal. 010 = normal operation 11x = divider reset 101 = bypass 15 stages (test mode only) 100 = bypass 10 stages (test mode only) 011 = bypass 5 stages (test mode only) 001 = invalid 000 = invalid 3:0 rate select (rs[3:0]) ? r/w. selects one of 13 taps of the 15 stage divider chain. the selected tap can generate a periodic interrupt if the pi e bit is set in register b. otherwise this tap will set the pf flag of register c. if the periodic interrupt is not to be used, these bits should all be set to 0. rs3 corresponds to bit 3. 0000 = interrupt never toggles 0001 = 3.90625 ms 0010 = 7.8125 ms 0011 = 122.070 s 0100 = 244.141 s 0101 = 488.281 s 0110 = 976.5625 s 0111 = 1.953125 ms 1000 = 3.90625 ms 1001 = 7.8125 ms 1010 = 15.625 ms 1011 = 31.25 ms 1100 = 62.5 ms 1101 = 125 ms 1110 = 250 ms 1111= 500 ms http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 442 datasheet 13.6.2.2 rtc_regb?register b (general configuration) rtc index: 0bh attribute: r/w default value: u0u00uuu (u: undefined) size: 8-bit lockable: no power well: rtc bit description 7 update cycle inhibit (set) ? r/w. enables/inhibits the update cycles. this bit is not affected by rsmrst# nor any other reset signal. 0 = update cycle occurs normally once each second. 1 = a current update cy cle will abort and subs equent update cycles will not occur until set is returned to 0. when set is one, the bios may in itialize time and calendar bytes safely. note: this bit should be set then cleared ea rly in bios post after each powerup directly after coin-cell battery insertion. 6 periodic interrupt enable (pie) ? r/w. this bit is cleare d by rsmrst#, but not on any other reset. 0 = disable. 1 = enable. allows an interrupt to occur with a time base set with the rs bits of register a. 5 alarm interrupt enable (aie) ? r/w. this bit is cleared by rtcrst#, but not on any other reset. 0 = disable. 1 = enable. allows an interrupt to occur when the af is set by an alarm match from the update cycle. an alarm can occur once a se cond, one an hour, once a day, or one a month. 4 update-ended interrupt enable (uie) ? r/w. this bit is cleared by rsmrst#, but not on any other reset. 0 = disable. 1 = enable. allows an interrupt to occur when the update cycle ends. 3 square wave enable (sqwe) ? r/w. this bit serves no functi on in the ich10. it is left in this register bank to provide compatibility with the motorola 146818b. the ich10 has no sqw pin. this bit is cleared by rsmrst#, but not on any other reset. 2 data mode (dm) ? r/w. this bit specifies either binary or bcd data representation. this bit is not affected by rs mrst# nor any other reset signal. 0 = bcd 1 = binary 1 hour format (hourform) ? r/w. this bit indicates the hour byte format. this bit is not affected by rsmrst# no r any other reset signal. 0 = twelve-hour mode. in twelve-hour mode, the seventh bit represents am as 0 and pm as one. 1 = twenty-four hour mode. 0 daylight savings legacy software support (dslsws) ? r/w. daylight savings functionality is no longer su pported. this bit is used to maintain legacy software support and has no associated functionality. if buc.dso bit is set, the dslsws bit continues to be r/w. http://www..net/ datasheet pdf - http://www..net/ datasheet 443 lpc interface bridge registers (d31:f0) 13.6.2.3 rtc_regc?register c (flag register) rtc index: 0ch attribute: ro default value: 00u00000 (u: undefined) size: 8-bit lockable: no power well: rtc writes to register c have no effect. 13.6.2.4 rtc_regd?register d (flag register) rtc index: 0dh attribute: r/w default value: 10uuuuuu (u: undefined) size: 8-bit lockable: no power well: rtc bit description 7 interrupt request flag (irqf) ? ro. irqf = (pf * pie) + (af * aie) + (uf *ufe). this bit also causes the rtc interrupt to be asserted. this bit is cleared upon rsmrst# or a read of register c. 6 periodic interrupt flag (pf) ? ro. this bit is cleared upon rsmrst# or a read of register c. 0 = if no taps are specified via the rs bits in register a, this flag will not be set. 1 = periodic interrupt flag will be 1 when the tap specified by the rs bits of register a is 1. 5 alarm flag (af) ? ro. 0 = this bit is cleared upon rtcrst# or a read of register c. 1 = alarm flag will be set after all alarm values match the current time. 4 update-ended flag (uf) ? ro. 0 = the bit is cleared upon rsmrst# or a read of register c. 1 = set immediately following an update cycle for each second. 3:0 reserved. will always report 0. bit description 7 valid ram and time bit (vrt) ? r/w. 0 = this bit should always be written as a 0 fo r write cycle, however it will return a 1 for read cycles. 1 = this bit is hardwired to 1 in the rtc power well. 6 reserved. this bit always returns a 0 and should be set to 0 for write cycles. 5:0 date alarm ? r/w. these bits store the date of month alarm value. if set to 000000b, then a don?t care state is as sumed. the host must configure the date alarm for these bits to do anything, yet they can be written at any time. if the date alarm is not enabled, these bits will return 0s to mimic the functionality of the motorola 146818b. these bits are not affected by any reset assertion. http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 444 datasheet 13.7 processor interface re gisters (lpc i/f?d31:f0) ta b l e 1 3 - 8 is the register address map for the processor interface registers. 13.7.1 nmi_sc?nmi status and control register (lpc i/f?d31:f0) i/o address: 61h attribute: r/w, ro default value: 00h size: 8-bit lockable: no power well: core table 13-8. processor interface pci re gister address map (lpc i/f?d31:f0) offset mnemonic register name default type 61h nmi_sc nmi status and control 00h r/w, ro 70h nmi_en nmi enable 80h r/w (special) 92h port92 fast a20 and init 00h r/w f0h coproc_err coprocessor error 00h wo cf9h rst_cnt reset control 00h r/w bit description 7 serr# nmi source status (serr#_nmi_sts) ? ro. 1 = bit is set if a pci agent detected a syst em error and pulses th e pci serr# line and if bit 2 (pci_serr_en) is cleared. this in terrupt source is enabled by setting bit 2 to 0. to reset the interrupt, set bit 2 to 1 and then set it to 0. when writing to port 61h, this bit must be 0. note: this bit is set by any of the ich10 intern al sources of serr; this includes serr assertions forwarded from the secondary pci bus, errors on a pci express* port, or other inte rnal functions that generate serr#. 6 iochk# nmi source status (iochk_nmi_sts) ? ro. 1 = bit is set if an lpc agent (via serirq) asserted iochk# and if bit 3 (iochk_nmi_en) is cleared. th is interrupt source is enabled by setting bit 3 to 0. to reset the interrupt, set bit 3 to 1 and then set it to 0. when writing to port 61h, this bit must be a 0. 5 timer counter 2 out status (tmr2_out_sts) ? ro. this bit reflects the current state of the 8254 counter 2 output. counter 2 must be programmed following any pci reset for this bit to have a de terminate value. when writing to port 61h, this bit must be a 0. 4 refresh cycle toggle (ref_toggle) ? ro. this signal toggles from either 0 to 1 or 1 to 0 at a rate that is equivalent to when refresh cycles would occur. when writing to port 61h, this bit must be a 0. 3 iochk# nmi enable (iochk_nmi_en) ? r/w. 0 = enabled. 1 = disabled and cleared. 2 pci serr# enable (pci_serr_en) ? r/w. 0 = serr# nmis are enabled. 1 = serr# nmis are di sabled and cleared. http://www..net/ datasheet pdf - http://www..net/ datasheet 445 lpc interface bridge registers (d31:f0) 13.7.2 nmi_en?nmi enable (and real time clock index) register (lpc i/f?d31:f0) i/o address: 70h attribute: r/w (special) default value: 80h size: 8-bit lockable: no power well: core note: the rtc index field is write-only for normal op eration. this field can only be read in alt- access mode. note, however, that this register is aliased to port 74h (documented in), and all bits are readable at that address. 13.7.3 port92?fast a20 and init register (lpc i/f?d31:f0) i/o address: 92h attribute: r/w default value: 00h size: 8-bit lockable: no power well: core 1 speaker data enable ( spkr_dat_en) ? r/w. 0 = spkr output is a 0. 1 = spkr output is equivalent to the counter 2 out signal value. 0 timer counter 2 enable (tim_cnt2_en) ? r/w. 0 = disable 1 = enable bit description bits description 7 nmi enable (nmi_en) ? r/w (special). 0 = enable nmi sources. 1 = disable all nmi sources. 6:0 real time clock index address (rtc_indx) ? r/w (special). th is data goes to the rtc to select which register or cmos ram address is being accessed. bit description 7:2 reserved 1 alternate a20 gate (alt_a20_gate) ? r/w. this bit is or?d with the a20gate input signal to generate a20m# to the processor. 0 = a20m# signal can po tentially go active. 1 = this bit is set when init# goes active. 0 init_now ? r/w. when this bit transitions fro m a 0 to a 1, the ich10 will force init# active for 16 pci clocks. http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 446 datasheet 13.7.4 coproc_err?coproc essor error register (lpc i/f?d31:f0) i/o address: f0h attribute: wo default value: 00h size: 8-bits lockable: no power well: core 13.7.5 rst_cnt?reset control register (lpc i/f?d31:f0) i/o address: cf9h attribute: r/w default value: 00h size: 8-bit lockable: no power well: core bits description 7:0 coprocessor error (coproc_err) ? wo. any value written to this register will cause ignne# to go active, if ferr# had ge nerated an internal irq13. for ferr# to generate an internal irq13, the coproc_err_en bit (chips et config regi sters:offset 31ffh: bit 1 for consumer family and offset 31feh: bit 9 for corporate family) must be 1. bit description 7:4 reserved 3 full reset (full_rst) ? r/w. this bit is used to de termine the states of slp_s3#, slp_s4#, and slp_s5# after a cf9 hard rese t (sys_rst =1 and rst_cpu is set to 1), after pwrok going low (with rsmrst# high), or after two tco timeouts. 0 = ich10 will keep slp_s3#, slp_s4# and slp_s5# high. 1 = ich10 will drive slp_s3#, slp_s4# and slp_s5# low for 3 ? 5 seconds. note: when this bit is set, it also causes the full power cycle (slp_s3/4/5# assertion) in response to sysreset#, pwrok# , and watchdog timer reset sources. 2 reset cpu (rst_cpu) ? r/w. when this bit transitions from a 0 to a 1, it initiates a hard or soft reset, as de termined by the sys_rst bit (bit 1 of this register). 1 system reset (sys_rst) ? r/w. this bit is used to determine a hard or soft reset to the processor. 0 = when rst_cpu bit goes from 0 to 1, the ich10 performs a soft reset by activating init# for 16 pci clocks. 1 = when rst_cpu bit goes from 0 to 1, the ich10 performs a hard reset by activating pltrst# and sus_stat# active for abou t 5-6 milliseconds. in this case, slp_s3#, slp_s4# and slp_s5# state (ass ertion or de-assertion) depends on full_rst bit setting. the ich10 main power well is reset when this bit is 1. it also resets the resume well bits (except for those noted throughout the eds). 0 reserved http://www..net/ datasheet pdf - http://www..net/ datasheet 447 lpc interface bridge registers (d31:f0) 13.8 power management registers (pm?d31:f0) the power management registers are distributed within the pci device 31: function 0 space, as well as a separate i/o range. each register is described below. unless otherwise indicate, bits are in the main (core) power well. bits not explicitly defined in each register are assumed to be reserved. when writing to a reserved bit, the value should always be 0. software should not attempt to use the value read from a reserved bit, as it may not be consistently 1 or 0. 13.8.1 power management pc i configuration registers (pm?d31:f0) table 13-9 shows a small part of the configuration space for pci device 31: function 0. it includes only those registers dedicated for power management. some of the registers are only used for legacy power management schemes. table 13-9. power management pci register address map (pm?d31:f0) offset mnemonic register name default type a0h gen_pmcon_1 general power management configuration 1 0000h r/w,, r/wo, ro a2h gen_pmcon_2 general power management configuration 2 00h r/w, r/wc a4h gen_pmcon_3 general power management configuration 3 00h r/w, r/wc a6h gen_pmcon_lo ck general power management configuration lock 00h ro, r/wlo a9h cx-state_cnf cx state configuration 00h r/w aah c4-timing_cnt c4 timing control 00h r/w abh bm_break_en bm_break_en 00h r/w ach pmir power management initialization 00000000h r/w, r/wl b8?bbh gpi_rout gpi route control 00000000h r/w http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 448 datasheet 13.8.1.1 gen_pmcon_1?general pm configuration 1 register (pm?d31:f0) offset address: a0h attribute: r/w, ro, r/wo default value: 0000h size: 16-bit lockable: no usage: acpi, legacy power well: core bit description 15:13 reserved 12 c4 disable ? r/w. this bit disabl es the c4 feature. 0 = enables c4 1 = disables c4. when c4 disable is 1: ? i/o reads to the lvl4 register will be retried normally, but with no other action ? all c4 transition attempts are disa bled, overriding c4onc3 and pop-down transition. 11 bmbusy# select (bmsel)? r/w. this bit along with gpio_use_sel[0] bit enables selection of bm_busy#/gpio0 func tion on ich pin as shown below: 10 bios_pci_exp_en ? r/w. this bit acts as a glob al enable for the sci associated with the pci express* ports. 0 = the various pci express ports and (g)mch cannot cause the pci_exp_sts bit to go active. 1 = the various pci express ports and (g)mch can cause the pci_exp_sts bit to go active. 9 pwrbtn_lvl ? ro. this bit indicates the curre nt state of the pwrbtn# signal. 0 = low. 1 = high. 8reserved 7 enter c4 when c3 invoked (c4onc3_en) ? r/w. if this bit is set, then when software does a lvl3 read, the ic h10 transitions to the c4 state. 6 (corporate only) ignore stop-grant - r/w. software sets this bit to indicate that the ich must not wait for the stop grant (aka req_c2) cycle. this bit must be set for ia64 processors and csi processors. 6 (consumer only) i64_en . software sets this bit to indicate that the processor is an ia_64 processor, not an ia_32 processor. this may be used in various state machines where there are behavioral differences. 5 (corporate only) reserved gpio_use_sel[0] bmsel pin function 1xgpio0 00bmbusy# 01reserved http://www..net/ datasheet pdf - http://www..net/ datasheet 449 lpc interface bridge registers (d31:f0) 5 (consumer only) cpu slp# enable (cpuslp_en) ? r/w. 0 = disable. 1 = enables the cpuslp# signal to go active in the s1 state. this reduces the processor power. note: cpuslp# will go active on entry to c3 and c4 states even if this bit is not set. 4 smi_lock ? r/wo. when this bit is set, writes to the glb_smi_en bit (pmbase + 30h, bit 0) will have no effect. once the smi_lock bit is set, writes of 0 to smi_lock bit will have no effect (i.e., on ce set, this bit can only be cleared by pltrst#). 3 reserved 2 pci clkrun# enable (clkrun_en) ? r/w. 0 = disable. ich10 drives the clkrun# signal low. 1 = enable clkrun# logic to control the system pci clock via the clkrun# and stp_pci# signals. note: when the slp_en# bit is set, the ich10 drives the clkrun# signal low regardless of the state of the clkrun_e n bit. this ensures that the pci and lpc clocks continue running during a transition to a sleep state. 1:0 periodic smi# rate select (per_smi_sel) ? r/w. set by software to control the rate at which periodic smi# is generated. 00 = 64 seconds 01 = 32 seconds 10 = 16 seconds 11 = 8 seconds bit description http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 450 datasheet 13.8.1.2 gen_pmcon_2?general pm configuration 2 register (pm?d31:f0) offset address: a2h attribute: r/w, r/wc default value: 00h size: 8-bit lockable: no usage: acpi, legacy power well: resume bit description 7 dram initialization bit ? r/w. this bit does not effect hardware functionality in any way. bios is expected to set this bit prior to starting the dram initialization sequence and to clear this bit after completing the dram initialization sequence. bios can detect that a dram initialization sequence was interru pted by a reset by re ading this bit during the boot sequence. ? if the bit is 1, then the dram initialization was interrupted. ? this bit is reset by the assertion of the rsmrst# pin. 6:5 cpu pll lock time (cplt) ? r/w. this field indicates the amount of time that the processor needs to lock its plls. this is used wherever timing t270 ( chapter 8 ) applies. 00 = min 30.7 s (default) 01 = min 61.4 s 10 = min 122.8 s 11 = min 42 s (min) to 48 s (max) it is the responsibility of the bios to program the correct value in this field prior to the first transition to c3 or c4 states. notes: 1. the dpslp-to-(g)mch message bits (d31:f 0:aah, bits 1:0) act as an override to these bits. 2. these bits are not cleared by any type of reset except rsmrst# or a cf9h write. 4 system reset status (srs) ? r/wc. software clears this bit by writing a 1 to it. 0 = sys_reset# button not pressed. 1 = ich10 sets this bit when the sys_reset# button is pressed. bi os is expected to read this bit and clear it, if it is set. notes: 1. this bit is also reset by rsmrst# and cf9h resets. 2. the sys_reset# is implemented in th e main power well. this pin must be properly isolated and masked to preven t incorrectly setting this suspend well status bit. 3 cpu thermal trip status (cts) ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = this bit is set when pltrst# is inactive and thrmtrip# goes active while the system is in an s0 or s1 state. notes: 1. this bit is also reset by rsmrst#, an d cf9h resets. it is not reset by the shutdown and reboot associated with the cputhrmtrip# event. 2. the cf9h reset in the desc ription refers to cf9h ty pe core well reset which includes sys_rst#, pwrok/ vrmpwrgd low, smbus hard reset, tco timeout. this type of reset will clear cts bit. http://www..net/ datasheet pdf - http://www..net/ datasheet 451 lpc interface bridge registers (d31:f0) 2 minimum slp_s4# assertion width violation status ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = hardware sets this bit when the slp_s4# assertion width is less than the time programmed in the slp_s4# minimum a ssertion width field (d31:f0:offset a4h:bits 5:4). the ich10 begins the timer when slp_s4# is asse rted during s4/s5 entry, or when the rsmrst# input is deasse rted during g3 exit. note that this bit is functional regardless of the value in the slp_s4# assertion stretch enable (d31:f0:offset a4h:bit 3). note: this bit is reset by the assertion of th e rsmrst# pin, but can be set in some cases before the default value is readable. 1 cpu power failure (cpupwr_flr) ? r/w. 0 = software (typically bios) clears this bit by writing a 0 to it. 1 = indicates that the vrmpwrgd signal from the processor?s vrm went low while the system was in an s0 or s1 state. note: vrmpwrgd is sampled using the rtc clock. therefore, low times that are less than one rtc clock period may not be detected by the intel ich10. 0 pwrok failure (pwrok_flr) ? r/wc. 0 = software clears this bit by writing a 1 to it, or when the system goes into a g3 state. 1 = this bit will be set any ti me pwrok goes low, when th e system was in s0, or s1 state. the bit will be cleared only by software by writing a 1 to this bit or when the system goes to a g3 state. note: see chapter 5.13.6.3 for more details about the pwrok pin functionality. note: in the case of true pwrok failure, pwrok will go low first before the vrmpwrgd. bit description http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 452 datasheet 13.8.1.3 gen_pmcon_3?general pm configuration 3 register (pm?d31:f0) offset address: a4h attribute: r/w, r/wc default value: 0000h consumer only size: 16-bit 0200h corporate only lockable: no usage: acpi, legacy power well: rtc, sus bit description 15 (corporate only) pme b0 s5 disable (pme_b0_s5_dis) ? r/w. when set to '1', this bit blocks wake events from pme_b0_sts in s5, rega rdless of the state of pme_b0_en. when cleared (default), wake events from pme_b0_sts are allowed in s5 if pme_b0_en = '1'. wakes from power states other than s5 are not affected by this policy bit. the net effect of setting pme_b0_s5_dis = '1' is described by the truth table below: y = wake; n = don't wake; b0 = pme_b0_en; ov = wol enable override this bit is cleared by the rtcrst# pin. 15 (consumer only) reserved 14 (corporate only) mac power down during wol disable ? r/w. 0 = mac power down wol is enabled if th e hardware and soft ware requirements are met. 1 = integrated mac remains powered whenever external suspend rails are powered. 13 (corporate only) wol enable override ? r/w. 0 = wol policies are determined by pmeb 0 enable bit and appropriate lan status bits 1 = enable integrated lan to wake the system in s5 only regardless of the value in the pme_b0_en bit in the gpe0_en register. this bit is cleared by the rtcrst# pin. 12 (corporate only) disable slp_s4# stretching after g3 : 0 = enables stretching on slp_s4# in co njunction with slp_s4# assertion stretch enable (bit 3) and the minimum assertion width (bits 5:4) 1 = disables stretching on slp_s4# re gardless of the state of the slp_s4# assertion stretch enable (bit 3). this bit is cleared by the rtcrst# pin. note: this field is ro when the slp_sx# stre tching policy lock- down bit is set. b0/ov s1/s3/s4 s5 00 n n 01 n y (lan only) 11 y (all pme b0 sources) y (lan only) 01 y (all pme b0 sources) n http://www..net/ datasheet pdf - http://www..net/ datasheet 453 lpc interface bridge registers (d31:f0) 11:10 (corporate only) slp_s3# minimum assertion width: this 2-bit value indicates the minimum assertion width of the slp_s3# signal to ensure that the main power supplies have been fully power-cycled. valid settings are: 00 = 60?100 us 01 = 1?1.2 ms 10 = 50?50.2 ms 11 = 2?2.0002 s this bit is cleared by the rsmrst# pin. note: this field is ro when the slp_sx# stretching policy lock-down bit is set. 14:10 (consumer only) reserved 9 general reset status (gen_rst_sts) ? r/wc. this bit is set by hardware whenever pltrst# asserts for any reason other than going into a software- entered sleep state (via pm1cnt.slp_en wr ite) or a suspend well power failure (rsmrst# pin assertion). bios is expected to consult and then write a ?1? to clear this bit during the boot flow before de termining what action to take based on pm1_sts.wak_sts = 1. if gen_rst_sts = ?1?, the cold reset boot path should be followed rather than the resume path, regardless of the setting of wak_sts. this bit is cleared by the rsmrst# pin. 8 s4_state# pin disable ? r/w. 0 = the traditional slp_s4# signal (without intel management engine overrides) is driven on the s4_state# pin. gpio26 defaults to its native functionality, s4_state#. 1 = the s4_state# pin functionality is disa bled. the pin is conf igured as gpio26, default as an output. note: this bit is cleared by rtcrst#. th is bit acts as an override for gpio_use_sel[26]. 7:6 swsmi_rate_sel ? r/w. this field indicates wh en the swsmi timer will time out. valid values are: 00 = 1.5 ms 0.6 ms 01 = 16 ms 4 ms 10 = 32 ms 4 ms 11 = 64 ms 4 ms these bits are not cleared by an y type of reset except rtcrst#. 5:4 slp_s4# minimum assertion width ? r/w. this field indicates the minimum assertion width of the slp_s4 # signal to ensure that th e drams have been safely power-cycled. valid values are: 11 = 1 to 2 seconds 10 = 2 to 3 seconds 01 = 3 to 4 seconds 00 = 4 to 5 seconds this value is used in two ways: 1. if the slp_s4# assertion width is ever shorter than this time, a status bit is set for bios to read when s0 is entered. 2. if enabled by bit 3 in this register , the hardware will prevent the slp_s4# signal from deasserting within this minimum time period after asserting. rtcrst# forces this field to the conservative default state (00b). note: this field is ro when the slp_s4# st retching policy lock-down bit is set. bit description http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 454 datasheet note: rsmrst# is sampled using the rtc clock. therefore, low times that are less than one rtc clock period may not be detected by the ich10. 3 slp_s4# assertion stretch enable ? r/w. 0 = the slp_s4# minimum assertion time is 1 to 2 rtcclk. 1 = the slp_s4# signal minimally assert for the time specified in bits 5:4 of this register. this bit is cleared by rtcrst#. note: this bit is ro when the slp_s4# stre tching policy lock-down bit is set. 2 rtc power status (rtc_pwr_sts) ? r/w. this bit is set when rtcrst# indicates a weak or missing battery. the bit is not cleared by any type of reset. the bit will remain set until the so ftware clears it by writing a 0 back to this bit position. 1 (corporate only) power failure (pwr_flr) ? r/wc. this bit is in the sus well, and defaults to a ?1? based on rsmrst# assertion (not cleared by any type of reset). 0 = indicates that the trickle current has not failed since the last time the bit was cleared. software clears this bit by writing a 1 to it. 1 = indicates that the trickle current (from the main battery or trickle supply) was removed or failed. 1 (consumer only) power failure (pwr_flr) ? r/wc. this bit is in the rtc well, and is not cleared by any type of reset except rtcrst#. 0 = indicates that the trickle current has not failed since the last time the bit was cleared. software clears this bit by writing a 1 to it. 1 = indicates that the trickle current (from the main battery or trickle supply) was removed or failed. note: clearing cmos in an ich-based platform can be done by using a jumper on rtcrst# or gpi, or using safemode strap. implementations should not attempt to clear cmos by using a jumper to pull vccrtc low. 0 (corporate only) afterg3_en ? r/w. this bit determines what state to go to when power is re- applied after a power failure (g3 state). 0 = system will return to s0 stat e (boot) after power is re-applied. 1 = system will return to the s5 state (except if it was in s4, in which case it will return to s4). in the s5 state, the only enabled wake event is the power button or any enabled wake event that was preserved through the power failure. this bit is cleared by rtcrst#. 0 (consumer only) afterg3_en ? r/w. this bit determines what state to go to when power is re- applied after a power failure (g3 state). th is bit is in the rtc well and is only cleared by writes of 06h or 0eh to cf9h (when the cf9h global reset bit is clear), receiving hard reset command with or without power cy cle from smbus or rtcrst#. 0 = system will return to s0 stat e (boot) after power is re-applied. 1 = system will return to the s5 state (except if it was in s4, in which case it will return to s4). in the s5 state, the only enabled wake event is the power button or any enabled wake event that was preserved through the power failure. note: this bit is set any time a power butt on override occurs (i.e., the power button is pressed for at least 4 consecutive seconds), due to the corresponding bit in the smbus uncondi tional power down message, due to an internal thermal sensor catastro phic condition and the assertion of thrmtrip#. bit description http://www..net/ datasheet pdf - http://www..net/ datasheet 455 lpc interface bridge registers (d31:f0) 13.8.1.4 gen_pmcon_lock- general powe r management configuration lock register offset address: a6h attribute: ro, r/wlo default value: 00h size: 8-bit lockable: no usage: acpi power well: core c bit description 7 unlocked c-state transition ? ro. this bit is set by hardware when a processor power state (c-state) transition deeper than c2 occurs and the c- state_config_lock bit is not set. this bit is cleared by pltrst# and is not writable by software. 6:3 reserved 2 slp_s4# stretching policy lock-down ? r/wlo. when set to 1, this bit locks down the slp_s4# minimum assertion wi dth, the slp_s4# assertion stretch enable (corporate only), the disable slp_s4# stretching after g3 (corporate only) and slp_s4# assertion stretch en able (consumer only) bits in the gen_pmcon_3 register, ma king them read-only. this bit becomes locked when a value of 1b is written to it. writes of 0 to this bit are always ignored. this bit is cleared by platform reset. 1 acpi_base_lock ? r/wlo. when set to 1, this bit locks down the acpi base address register (abase) at offset 40h. the base a ddress field becomes read- only. this bit becomes locked when a value of 1b is written to it. writes of 0 to this bit are always ignored. once locked by writing 1, the only way to clear this bit is to perform a platform reset. 0 c-state_config_lock ? r/wlo. when set to 1, this bit locks down the c-state configuration parameters. the following configuration bits become read-only when this bit is set: ? ia64_en (gen_pmcon_1, bit 6) ? c4_disable (gen_pmcon_1, bit 12) ? cpu_pll_lock_time (gen_pmcon_2, bits 6:5) ? the entire c4 timing control register (c4_timing_cnt) this bit becomes locked when a value of 1b is written to it. writes of 0 to this bit are always ignored. once locked by writing 1, the only way to clear this bit is to perform a platform reset. http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 456 datasheet 13.8.1.5 cx-state_cnf?cx state configuration register (pm?d31:f0) offset address: a9h attribute: r/w default value: 00h size: 8-bit lockable: no usage: acpi, legacy power well: core this register is used to enable c-state related modes. bit description 7 scratchpad (sp) ? r/w. 6:5 reserved 4 popdown mode enable (pdme) ? r/w. this bit is used in conjunction with the pume bit (d31:f0:a9h, bit 3). if pume is 0, then this bit must also be 0. 0 = the ich10 will not attempt to automatically return to a previous c3 or c4 state. 1 = when this bit is a 1 and ich10 observes that there are no bus master requests, it can return to a previous c3 or c4 state. note: this bit is separate from the pume bi t to cover cases where latency issues permit popup but not popdown. 3 popup mode enable (pume) ? r/w. when this bit is a 0, the ich10 behaves like ich5, in that bus master traffic is a break ev ent, and it will retu rn from c3/c4 to c0 based on a break event. see chapter 5.13.5 for additional deta ils on this mode. 0 = the ich10 will treat bus master traffic a break event, and will return from c3/c4 to c0 based on a break event. 1 = when this bit is a 1 and ich10 observes a bus master request, it will take the system from a c3 or c4 state to a c2 stat e and auto enable bus masters. this will let snoops and memory access occur. 2 report zero for bm_sts (bm_sts_zero_en) ? r/w. 0 = the ich10 sets bm_sts (pmbase + 00h, bit 4) if there is bus master activity from pci, pci express* and internal bus masters. 1 = when this bit is a 1, ich10 will not set the bm_sts if there is bus master activity from pci, pci express an d internal bus masters. notes: 1. if the bm_sts bit is already set when the bm_sts_zero_en bit is set, the bm_sts bit will remain set. software wi ll still need to clear the bm_sts bit. 2. it is expected that if the pume bi t (this register, bit 3) is set, the bm_sts_zero_en bit should also be set. 3. bm_sts will be set by lpc dma or lp c masters, even if bm_sts_zero_en is set. 1:0 reserved http://www..net/ datasheet pdf - http://www..net/ datasheet 457 lpc interface bridge registers (d31:f0) 13.8.1.6 c4-timing_cnt?c4 timing control register (pm?d31:f0) offset address: aah attribute: r/w default value: 00h size: 8-bit lockable: no usage: acpi, legacy power well: core this register is used to enable c-state related modes. bit description 7 reserved 6 slow-c4 exit enable ?when 1, this bit enables the slow-c4 exit functionality. 5:4 reserved 3:2 dprslpvr to stpcpu ? r/w. this field selects the am ount of time that the ich10 waits for from the deassertion of dprslpvr to the deassertion of stp_cpu#. this provides a programmable time for the processor?s voltage to stabilize when exiting from a c4 state. this thus changes the value for t266a. 1:0 dpslp-to-mch message ? r/w. this field selects the dpslp# deassertion to (g)mch message time (t270). normally this value is determined by the cpu_pll_lock_time field in th e gen_pmcon_2 register. when this field is non-zero, then the values in this register have higher priority. it is software?s responsibility to program these fields in a consistent manner. bits t266a min t266a max comment 00b 95 s 101 s default 01b 22 s 28 s value used for ?fast? vrms 10b 34 s 40 s value used for ?fast? vrms 11b reserved bits t270 00b use value is cpu_pll_lock_time field (default is 30 s) 01b 20 s 10b 15 s 11b 10 s http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 458 datasheet 13.8.1.7 bm_break_en register (pm?d31:f0) offset address: abh attribute: r/w default value: 00h size: 8-bit lockable: no usage: acpi, legacy power well: core bit description 7 storage_break_en ? r/w. 0 = serial ata traffic will not act as a break event. 1 = serial ata traffic acts as a break ev ent, even if the bm_sts-zero_en and popup_en bits are set. serial ata master activity will cause bm_sts to be set and will cause a break from c3/c4. 6 pcie_break_en ? r/w. 0 = pci express* traffic will not act as a break event. 1 = pci express traffic acts as a break event, even if the bm_sts-zero_en and popup_en bits are set. pci express master activity will cause bm_sts to be set and will cause a break from c3/c4. 5 pci_break_en ? r/w. 0 = pci traffic will no t act as a break event. 1 = pci traffic acts as a break event, even if the bm_sts-zero_en and popup_en bits are set. pci master activity will cause bm_sts to be set and will cause a break from c3/c4. 4:3 reserved 2 ehci_break_en ? r/w. 0 = ehci traffic will not act as a break event. 1 = ehci traffic acts as a break event, even if the bm_sts-zero_en and popup_en bits are set. ehci master activity will cause bm_sts to be set and will cause a break from c3/c4. 1 uhci_break_en ? r/w. 0 = uhci traffic will not act as a break event. 1 = usb traffic from any of the internal uh cis acts as a break event, even if the bm_sts-zero_en and popup_en bits are se t. uhci master activity will cause bm_sts to be set and will cause a break from c3/c4. 0 hda_break_en ? r/w. 0 = intel ? high definition audio traffic will not act as a break event. 1 = intel high definition audio traffic acts as a break event, even if the bm_sts- zero_en and popup_en bits are set. intel high definition audio master activity will cause bm_sts to be set and will cause a break from c3/c4. http://www..net/ datasheet pdf - http://www..net/ datasheet 459 lpc interface bridge registers (d31:f0) 13.8.1.8 pmir?power management in itialization register (pm?d31:f0) offset address: ach attribute: r/w default value: 00000000h size: 32-bit 0 13.8.1.9 gpio_rout?gpio routing control register (pm?d31:f0) offset address: b8h ? bbh attribute: r/w default value: 00000000h size: 32-bit lockable: no power well: resume note: gpios that are not implemented will not have the corresponding bits implemented in this register. bit description 31 cf9h lockdown (cf9lock): when set, this bit locks the bits in this register into their current value. this register is rese t by a cf9h reset. 30 pmir field 2 ? r/w. bios must program this bit to 1b. 29:21 reserved 20 cf9h global reset (cf9gr) ? r/w. when set, a cf9h write of 6h or eh will cause a global reset of both the host and intel me part itions. if this bit is cleared, a cf9h write of 6h or eh will only reset th e host partition. this bit fiel d is not reset by a cf9h reset. 19:15 reserved 14 intel ? at host reset trigger enable - r/w. when set this bit enables bits [1:0] in the cir11 register. 13:10 reserved 9:8 pmir field 0 ? r/w. bios must program these bits to 11b. 7:0 reserved bit description 31:30 gpio15 route ? r/w. see bits 1:0 for description. same pattern for gpio14 through gpio3 5:4 gpio2 route ? r/w. see bits 1:0 for description. 3:2 gpio1 route ? r/w. see bits 1:0 for description. 1:0 gpio0 route ? r/w. gpio[15:0] can be routed to cause an smi or sci when the gpio[n]_sts bit is set. if the gpio0 is not set to an input, this field has no effect. if the system is in an s1?s5 state and if the gpe0_en bit is also set, then the gpio can cause a wake event, even if the gpio is not routed to cause an smi# or sci. 00 = no effect. 01 = smi# (if corresponding alt_gpi_smi_en bit is also set) 10 = sci (if corresponding gpe0_en bit is also set) 11 = reserved http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 460 datasheet 13.8.2 apm i/o decode table 13-10 shows the i/o registers associated with apm support. this register space is enabled in the pci device 31: function 0 space (apmdec_en), and cannot be moved (fixed i/o location). 13.8.2.1 apm_cnt?advanced power ma nagement control port register i/o address: b2h attribute: r/w default value: 00h size: 8-bit lockable: no usage: legacy only power well: core 13.8.2.2 apm_sts?advanced power management status port register i/o address: b3h attribute: r/w default value: 00h size: 8-bit lockable: no usage: legacy only power well: core table 13-10. apm register map address mnemonic register name default type b2h apm_cnt advanced power management control port 00h r/w b3h apm_sts advanced power management status port 00h r/w bit description 7:0 used to pass an apm command between the os and the smi handler. writes to this port not only store data in the apmc regi ster, but also generates an smi# when the apmc_en bit is set. bit description 7:0 used to pass data between the os and the smi handler. basically, this is a scratchpad register and is not affected by any other register or functi on (other than a pci reset). http://www..net/ datasheet pdf - http://www..net/ datasheet 461 lpc interface bridge registers (d31:f0) 13.8.3 power management i/o registers table 13-11 shows the registers associated with acpi and legacy power management support. these registers are enabled in the pci device 31: function 0 space (pm_io_en), and can be moved to any i/o lo cation (128-byte aligned). the registers are defined to support the acpi 3.0a spec ification, and use the same bit names. note: all reserved bits and registers will always re turn 0 when read, and will have no effect when written. table 13-11. acpi and le gacy i/o register map pmbase + offset mnemonic register name acpi pointer default type 00h?01h pm1_sts pm1 status pm1a_evt_blk 0000h r/wc 02h?03h pm1_en pm1 enable pm1a_evt_blk+2 0000h r/w 04h?07h pm1_cnt pm1 control pm1a_cnt_blk 00000000h r/w, wo 08h?0bh pm1_tmr pm1 timer pmtmr_blk xx000000h ro 0ch?0fh ? reserved ? ? ? 10h?13h proc_cnt processor control p_blk 00000000h r/w, ro, wo 14h lv2 level 2 p_blk+4 00h ro 15h lv3 level 3 p_blk+5 00h ro 16h lv4 level 4 p_blk+6 00h ro 17h?18h ? reserved ? ? ? 19h?1fh ? reserved ? ? ? 20-27h gpe0_sts general purpose event 0 status gpe0_blk 00000000h r/wc 28-2fh gpe0_en general purpose event 0 enables gpe0_blk+8 00000000h r/w 30h?33h smi_en smi# control and enable 00000000h (consumer); 00000002h (corporate) r/w, wo, r/wo 34h?37h smi_sts smi status 00000000h r/wc, ro 38h?39h alt_gp_smi_en altern ate gpi smi enable 0000h r/w 3ah?3bh alt_gp_smi_st s alternate gpi smi status 0000h r/wc 3ch uprwc usb per-port registers write control 0000h r/wc, ro, r/wo 3dh?41h ? reserved ? ? ? 42h gpe_cntl general purpose event control 00h ro, r/w 43h ? reserved ? ? ? 44h?45h devact_sts device ac tivity status 0000h r/wc 46h?4fh ? reserved 50h pm2_cnt pm2 control pm2a_cnt_blk 00h r/w 51h-53h ? reserved 54h?57h c3_res c3-residency register ? 00000000h ro 58h-5bh ? reserved 5ch?5fh ? reserved ? ? ? 60h?7fh ? reserved for tco ? ? ? http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 462 datasheet 13.8.3.1 pm1_sts?power mana gement 1 status register i/o address: pmbase + 00h ( acpi pm1a_evt_blk ) attribute: r/wc default value: 0000h size: 16-bit lockable: no usage: acpi or legacy power well: bits 0 ? 7: core, bits 8 ? 15: resume, except bit 11 in rtc if bit 10 or 8 in this register is set, and the corresponding _en bit is set in the pm1_en register, then the ich10 will generate a wake event. once back in an s0 state (or if already in an s0 state when the event occurs ), the ich10 will also generate an sci if the sci_en bit is set, or an smi# if the sci_en bit is not set. note: bit 5 does not cause an smi# or a wake event. bit 0 does not cause a wake event but can cause an smi# or sci. bit description 15 wake status (wak_sts) ? r/wc. this bit is not affected by hard resets caused by a cf9 write, but is reset by rsmrst#. 0 = software clears this bit by writing a 1 to it. 1 = set by hardware when the system is in one of the sleep states (via the slp_en bit) and an enabled wake event occurs. upon setting this bit, the ich10 will transition the system to the on state. if the afterg3_en bit is not set and a power failure occurs without the slp_en bit set, the system will return to an s0 st ate when power returns, and the wak_sts bit will not be set. if the afterg3_en bit is set and a power failure occurs without the slp_en bit having been set, the system will go into an s5 state when power returns, and a subsequent wake event will cause the wak_sts bit to be set. note that any subsequent wake event would have to be ca used by either a power button press, or an enabled wake event that was preserved through the power failure (enable bit in the rtc well). 14 pci express wake status (pciexpwak_sts) ? r/wc. 0 = software clears this bit by writing a 1 to it. if the wake# pin is still active during the write or the pme message received indication has not been cleared in the root port, then the bit will remain active (i.e. all inputs to this bit are level- sensitive). 1 = this bit is set by hardware to indica te that the system woke due to a pci express wakeup event. this wakeup event can be caused by the pci express wake# pin being active or receipt of a pci express pme message at a root port. this bit is set only when one of these events causes the system to transition from a non-s0 system power state to the s0 system power state. this bit is set independent of the state of the pciexp_wake_dis bit. note: this bit does not itself cause a wake event or prevent entry to a sleeping state. thus if the bit is 1 and the system is put into a sleeping state, the system will not automatically wake. 13:12 reserved http://www..net/ datasheet pdf - http://www..net/ datasheet 463 lpc interface bridge registers (d31:f0) 11 power button override status (pwrbtnor_sts) ? r/wc. 0 = software clears this bi t by writing a 1 to it. 1 = this bit is set any time a power button ov erride occurs (i.e., the power button is pressed for at least 4 consecutive seconds), due to the corresponding bit in the smbus slave message, intel me initiated power button override, intel me initiated host reset with power down or due to an internal thermal sensor catastrophic condition. the power butt on override causes an unconditional transition to the s5 state, as well as sets the afterg3_en bit. the bios or sci handler clears this bit by writing a 1 to it . this bit is not affected by hard resets via cf9h writes, and is not reset by rsmrst#. thus, this bit is preserved through power failures. note that if this bit is still asserted when the global sci_en is set then an sci will be generated. 10 rtc status (rtc_sts) ? r/wc. this bit is not affected by hard resets caused by a cf9 write, but is reset by rsmrst#. 0 = software clears this bi t by writing a 1 to it. 1 = set by hardware when the rtc genera tes an alarm (asser tion of the irq8# signal). additionally if th e rtc_en bit (pmbase + 02h, bit 10) is set, the setting of the rtc_sts bit will generate a wake event. 9 me_sts ? r/wc. this bit is set when the in tel management engine generates a non-maskable wake event, and is not affected by any other enable bit. when this bit is set, the host power management logic wakes to s0. this bit is only set by hardware and can on ly be reset by writin g a one to this bit position. this bit is not affected by hard re sets caused by a cf9 wr ite, but is reset by rsmrst#. 8 power button status ( pwrbtn__sts) ? r/wc. this bit is not affected by hard resets caused by a cf9 write. 0 = if the pwrbtn# signal is held low for mo re than 4 seconds, the hardware clears the pwrbtn_sts bit, sets the pwrbtnor_sts bit, and the system transitions to the s5 state with only pwrbtn# enabled as a wake event. this bit can be cleared by software by writing a one to the bit position. 1 = this bit is set by hard ware when the pwrbtn# si gnal is asserted low, independent of any other enable bit. in the s0 state, while pwrbtn_en and pwrbtn_sts are both set, an sci (or smi# if sci_en is not set) will be generated. in any sleeping state s1?s5, while pwrbtn_en (pmbase + 02h, bit 8) and pwrbtn_sts are both set, a wake event is generated. note: if the pwrbtn_sts bit is cleared by software while the pwrbtn# signal is sell asserted, this will not cause the pwrbn_sts bit to be set. the pwrbtn# signal must go inactive and active again to set the pwrbtn_sts bit. 7:6 reserved 5 global status (gbl _sts) ? r/wc. 0 = the sci handler should then clear this bit by writing a 1 to the bit location. 1 = set when an sci is generated due to bios wanting the attention of the sci handler. bios has a corresponding bit, bios_rls, which will cause an sci and set this bit. bit description http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 464 datasheet 4 bus master status (bm_sts) ? r/wc. this bit will not cause a wake event, sci or smi#. 0 = software clears this bit by writing a 1 to it. 1 = set by the ich10 when a bus master requests access to main memory. bus master activity is detected by any of the pci requests being active, any internal bus master request being active, or req-c2 message received while in c3 or c4 state. note: 1. if the bm_sts_zero_en bit is set, then this bit will generally report as a 0. lpc dma and bus master activity will always set the bm_sts bit, even if the bm_sts_zero_en bit is set. 3:1 reserved 0 timer overflow status (tmrof_sts) ? r/wc. 0 = the sci or smi# handler clears this bit by writing a 1 to the bit location. 1 = this bit gets set any time bit 22 of the 24-bit timer goes high (bits are numbered from 0 to 23). this will occur every 2.3435 seconds. when the tmrof_en bit (pmbase + 02h, bit 0) is set, then the setting of the tmrof_sts bit will additionally generate an sci or smi# (depending on the sci_en). bit description http://www..net/ datasheet pdf - http://www..net/ datasheet 465 lpc interface bridge registers (d31:f0) 13.8.3.2 pm1_en?power management 1 enable register i/o address: pmbase + 02h ( acpi pm1a_evt_blk + 2 ) attribute: r/w default value: 0000h size: 16-bit lockable: no usage: acpi or legacy power well: bits 0 ? 7: core, bits 8 ? 9, 11 ? 15: resume, bit 10: rtc bit description 15 reserved 14 pci express* wake disable(pciexpwak_dis) ? r/w. modification of this bit has no impact on the value of the pciexp_wake_sts bit. 0 = inputs to the pciexp_wake_sts bit in th e pm1 status register enabled to wake the system. 1 = inputs to the pciexp_wake_sts bit in the pm1 status regi ster disabled from waking the system. 13:11 reserved 10 rtc event enable (rtc_en) ? r/w. this bit is in the rtc well to allow an rtc event to wake after a power failure. this bit is not cleared by any reset other than rtcrst# or a power button override event. 0 = no sci (or smi#) or wake event is generated then rtc_sts (pmbase + 00h, bit 10) goes active. 1 = an sci (or smi#) or wake event will occur when this bit is set and the rtc_sts bit goes active. 9reserved. 8 power button enab le (pwrbtn_en) ? r/w. this bit is used to enable the setting of the pwrbtn_sts bit to generate a power management event (smi#, sci). pwrbtn_en has no effect on the pwrbtn_sts bit (pmbase + 00h, bi t 8) being set by the assertion of the power button. the powe r button is always enabled as a wake event. 0 = disable. 1 = enable. 7:6 reserved. 5 global enable (gbl_en) ? r/w. when both the gbl_en and the gbl_sts bit (pmbase + 00h, bit 5) are set, an sci is raised. 0 = disable. 1 = enable sci on gbl_sts going active. 4:1 reserved. 0 timer overflow interrupt enable (tmrof_en) ? r/w. works in conjunction with the sci_en bit (pmbase + 04h, bit 0) as described below: tmrof_en sci_en effect when tmrof_sts is set 0 x no smi# or sci 10 smi# 11 sci http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 466 datasheet 13.8.3.3 pm1_cnt?power management 1 control i/o address: pmbase + 04h ( acpi pm1a_cnt_blk ) attribute: r/w, wo default value: 00000000h size: 32-bit lockable: no usage: acpi or legacy power well: bits 0 ? 7: core, bits 8 ? 12: rtc, bits 13 ? 15: resume bit description 31:14 reserved. 13 sleep enable ( slp_en) ? wo. setting this bit causes the system to sequence into the sleep state defined by the slp_typ field. 12:10 sleep type (slp_typ) ? r/w. this 3-bit field defi nes the type of sleep the system should enter when the slp_en bit is set to 1. these bits are only reset by rtcrst#. 9:3 reserved. 2 global release (gbl_rls) ? wo. 0 = this bit always reads as 0. 1 = acpi software writes a 1 to this bit to raise an event to the bios. bios software has a corresponding enable and status bits to control its ability to receive acpi events. 1 bus master reload (bm_rld) ? r/w. this bit is treated as a scratchpad bit. this bit is reset to 0 by pltrst# 0 = bus master requests will not cause a break from the c3 state. 1 = enables bus master requests (internal or external) to cause a break from the c3 state. if software fails to set this bit before goin g to c3 state, ich10 will still return to a snoopable state from c3 or c4 st ates due to bus master activity. 0 sci enable ( sci_en) ? r/w. selects the sci interrupt or the smi# interrupt for various events including the bits in the pm1_ sts register (bit 10, 8, 0), and bits in gpe0_sts. 0 = these events will generate an smi#. 1 = these events will generate an sci. code master interrupt 000b on: typically maps to s0 state. 001b asserts stpclk#. puts processor in stop-grant state. optional to assert cpuslp# to put processor in sleep state: typically maps to s1 state. 010b reserved 011b reserved 100b reserved 101b suspend-to-ram. assert slp_s3 #: typically maps to s3 state. 110b suspend-to-disk. assert slp_s3#, and slp_s4#: typically maps to s4 state. 111b soft off. assert slp_s3#, slp_s4#, and slp_s5#: typically maps to s5 state. http://www..net/ datasheet pdf - http://www..net/ datasheet 467 lpc interface bridge registers (d31:f0) 13.8.3.4 pm1_tmr?power management 1 timer register i/o address: pmbase + 08h ( acpi pmtmr_blk ) attribute: ro default value: xx000000h size: 32-bit lockable: no usage: acpi power well: core 13.8.3.5 proc_cnt?processor control register i/o address: pmbase + 10h ( acpi p_blk ) attribute: r/w, ro, wo default value: 00000000h size: 32-bit lockable: no (bits 7:5 are write once)usage: acpi or legacy power well: core bit description 31:24 reserved 23:0 timer value (tmr_val) ? ro. returns the running count of the pm timer. this counter runs off a 3.579545 mhz clock (14.31818 mhz divided by 4). it is reset to 0 during a pci reset, and then continues counting as long as the system is in the s0 state. after an s1 state, the counter will not be reset (it will continue counting from the last value in s0 state. anytime bit 22 of the timer goes high to low (bits referenced from 0 to 23), the tmrof_sts bit (pmbase + 00h, bit 0) is set. the high-to-low transition will occur every 2.3435 seconds. if the tmrof_en bit (pmbase + 02h, bit 0) is set, an sci interrupt is also generated. bit description 31:18 reserved 17 throttle status (thtl_sts) ? ro. 0 = no clock throttling is occurring (maximum processor performance). 1 = indicates that the clock state machine is throttling the processor performance. this could be due to the tht_en bit or the force_thtl bit being set. 16:9 reserved 8 force thermal throttling (force_thtl) ? r/w. software can se t this bit to force the thermal throttling function. 0 = no forced throttling. 1 = throttling at the duty cycle specified in thrm_dty starts immediately, and no smi# is generated. http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 468 datasheet 7:5 thrm_dty ? wo. this write-once fi eld determines the duty cycle of the throttling when the force_thtl bit is set. the duty cycle indicates the a pproximate percentage of time the stpclk# signal is asserted while in the throttle mode. the stpclk# throttle period is 1024 pciclks. note that the throttling only occurs if the system is in the c0 state. if in the c2, c3, or c4 state, no throttling occurs. once the thrm_dty field is written, any subs equent writes will have no effect until pltrst# goes active. 4 thtl_en ? r/w. when set and the system is in a c0 state, it enables a processor- controlled stpclk# throttling. the duty cy cle is selected in the thtl_dty field. 0 = disable 1 = enable 3:1 thtl_dty ? r/w. this field determines the duty cycle of the throttling when the thtl_en bit is set. the duty cycle indicate s the approximate percentage of time the stpclk# signal is asserted (low) while in the throttle mode. the stpclk# throttle period is 1024 pciclks. 0 reserved bit description thrm_dty throttle mode pci clocks 000b 50% (default) 512 001b 87.5% 896 010b 75.0% 768 011b 62.5% 640 100b 50% 512 101b 37.5% 384 110b 25% 256 111b 12.5% 128 thtl_dty throttle mode pci clocks 000b 50% (default) 512 001b 87.5% 896 010b 75.0% 768 011b 62.5% 640 100b 50% 512 101b 37.5% 384 110b 25% 256 111b 12.5% 128 http://www..net/ datasheet pdf - http://www..net/ datasheet 469 lpc interface bridge registers (d31:f0) 13.8.3.6 lv2 ? level 2 register i/o address: pmbase + 14h ( acpi p_blk+4 ) attribute: ro default value: 00h size: 8-bit lockable: no usage: acpi or legacy power well: core note: this register should not be used by ia-64 pr ocessors or systems with more than 1 logical processor, unless appropriate semaphoring software has been put in place to ensure that all threads/processors are read y for the c2 state when the re ad to this register occurs 13.8.3.7 lv3?level 3 register i/o address: pmbase + 15h (acpi p_blk + 5) attribute: ro default value: 00h size: 8-bit lockable: no usage: acpi or legacy power well: core note: if the c4onc3_en bit is set, reads this register will initiate a lvl4 transition rather than a lvl3 transition. in the event that software at tempts to simultaneous ly read the lvl2 and lvl3 registers (which is invalid), the ich10 wi ll ignore the lvl3 read, and only perform a c2 transition. note: this register should not be used by ia-64 pr ocessors or systems with more than 1 logical processor, unless appropriate semaphoring software has been put in place to ensure that all threads/processors are read y for the c3 state when the re ad to this register occurs. 13.8.3.8 lv4?level 4 register i/o address: pmbase + 16h (acpi p_blk + 6) attribute: ro default value: 00h size: 8-bit lockable: no usage: acpi or legacy power well: core note: this register should not be used by ia-64 pr ocessors or systems with more than 1 logical processor, unless appropriate semaphoring software has been put in place to ensure that all threads/processors are read y for the c4 state when the re ad to this register occurs. bit description 7:0 reads to this register return all 0s, writes to this register have no effect. reads to this register generate a ?enter a level 2 power state? (c2) to the clock control logic. this will cause the stpclk# signal to go active, and stay active until a break event occurs. throttling (due either to thtl_en or force_thtl) will be ignored. bit description 7:0 reads to this register return al l 0s, writes to this register have no effect. reads to this register generate a ?enter a c3 power state? to the clock control logic. the c3 state persists until a break event occurs. bit description 7:0 reads to this register return al l 0s, writes to this register have no effect. reads to this register generate a ?enter a c4 power state? to the clock control logic. the c4 state persists until a break event occurs. http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 470 datasheet 13.8.3.9 gpe0_sts?general purpose event 0 status register i/o address: pmbase + 20h (acpi gpe0_blk) attribute: bits 0:32 r/wc bits 33:63 ro default value: 0000000000000000h size: 64-bit lockable: no usage: acpi power well: resume this register is symmetrical to the gene ral purpose event 0 enable register. unless indicated otherwise below, if the corresponding _en bit is set, then when the _sts bit get set, the ich10 will generate a wake event. once back in an s0 state (or if already in an s0 state when the event occurs), th e ich10 will also generate an sci if the sci_en bit is set, or an smi# if the sci_en bit (pmbase + 04h, bit 0) is not set. bits 31:16 are reset by a cf9h write; bits 63:32 and 15:0 are not. all are reset by rsmrst#. bit description 63:33 reserved. 32 usb6_sts ? r/wc. 0 = disable. 1 = set by hardware and can be reset by writing a one to this bit position or a resume well reset. this bit is set when usb uhci controller #6 needs to cause a wake. additionally if the usb6_en bit is set, the setting of the usb6_sts bit will generate a wake event. 31:16 gpion_sts ? r/wc. 0 = software clears this bi t by writing a 1 to it. 1 = these bits are set any time the correspon ding gpio is set up as an input and the corresponding gpio signal is high (or low if the corresponding gp_inv bit is set). if the corresponding enable bit is set in the gpe0_en register, then when the gpio[n]_sts bit is set: ? if the system is in an s1?s5 state, the event will also wake the system. ? if the system is in an s0 state (or upon wa king back to an s0 state), a sci will be caused depending on the gpio_rout bits (d31:f0:b8h, bits 31:30) for the corresponding gpi. note: mapping is as follows: bit 31 corre sponds to gpio[15]... and bit 16 corresponds to gpio[0]. 15 reserved 14 usb4_sts ? r/wc. 0 = disable. 1 = set by hardware and can be reset by writing a one to this bit position or a resume well reset. this bit is set when usb uhci controller #4 needs to cause a wake. additionally if the usb4_en bit is set, the setting of the usb4_sts bit will generate a wake event. http://www..net/ datasheet pdf - http://www..net/ datasheet 471 lpc interface bridge registers (d31:f0) 13 pme_b0_sts ? r/wc. this bit will be set to 1 by the ich10 when any internal device with pci power management capabiliti es on bus 0 asserts the equivalent of the pme# signal. additionally, if the pme_b0_en bit is set, and the sy stem is in an s0 state, then the setting of the pme_b0_sts bit will generate an sci (or smi# if sci_en is not set). if the pme_b0_sts bit is set, and the system is in an s1?s4 state (or s5 state due to slp_typ and slp_en), then the setting of the pme_b0_sts bit will generate a wake event, and an sci (o r smi# if sci_en is not set) will be generated. if the system is in an s5 state due to power button override, then the pme_b0_sts bit will not cause a wake event or sci. the default for this bit is 0. writing a 1 to this bit position clears this bit. note : hd audio wake events are reported in this bit. intel management engine ?maskable? wake events are also reported in this bit. 12 usb3_sts ? r/wc. 0 = disable. 1 = set by hardware and can be reset by writing a one to this bit position or a resume well reset. this bit is set when usb uhci controller #3 needs to cause a wake. additionally if the usb3_en bit is set, the setting of the usb3_sts bit will generate a wake event. 11 pme_sts ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = set by hardware when the pme# signal goes active. additionally, if the pme_en bit is set, and the system is in an s0 state, then the setting of the pme_sts bit will generate an sci or smi# (if sci_en is not set). if the pme_en bit is set, and the system is in an s1?s4 state (or s5 state due to setting slp_typ and slp_en), then the setting of the pme_sts bit will generate a wake event, and an sci will be generated. if the system is in an s5 state due to power button override or a power failure, then pme_ sts will not cause a wake event or sci. 10 reserved 9 pci_exp_sts ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = set by hardware to indicate that: ? the pme event message was received on one or more of the pci express* ports ? an assert pmegpe me ssage received from the (g)mch via dmi notes: 1. the pci wake# pin has no impact on this bit. 2. if the pci_exp_sts bit went active due to an assert pmegpe message, then a deassert pmegpe message mu st be received prior to the software write in order for the bit to be cleared. 3. if the bit is not cleared and the corre sponding pci_exp_en bit is set, the level-triggered sci will remain active. 4. a race condition exists where the pci express device sends another pme message because the pci express device was not serviced within the time when it must resend the message. this may result in a spurious interrupt, and this is comprehended and approved by the pci express* specification, revision 1.0a . the window for this race condition is approximately 95?105 milliseconds. 8 ri_sts ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = set by hardware when the ri# input signal goes active. bit description http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 472 datasheet 7 smbus wake status (smb_wak_sts) ? r/wc. the smbus controller can independently cause an smi# or sci, so this bit does not need to do so (unlike the other bits in this register). software clears this bit by writing a 1 to it. 0 = wake event not caused by the ich10?s smbus logic. 1 = set by hardware to indicate that th e wake event was caused by the ich10?s smbus logic.this bit will be set by the wake/smi# command type, even if the system is already awake. the smi ha ndler should then clear this bit. notes: 1. the smbus controller will independently cause an smi# so this bit does not need to do so (unlike the ot her bits in this register). 2. this bit is set by the smbus slave command 01h (wake/smi#) even when the system is in the s0 state. therefore, to avoid an instant wake on subsequent transitions to sleep states, software must clear this bit after each reception of the wake/smi# command or just pr ior to entering the sleep state. 3. (consumer only) if smb_wak_sts is set due to smbus slave receiving a message, it will be cl eared by internal logic when a thrmtrip# event happens or a power button override event. however, thrmtrip# or power button override event will not clea r smb_wak_sts if it is set due to smbalert# signal going active. 4. the smbalert_sts bit (d31:f3:i/o offs et 00h:bit 5) shou ld be cleared by software before the smb_ wak_sts bit is cleared. 6 tcosci_sts ? r/wc. software clears this bit by writing a 1 to it. 0 = toc logic or thermal sens or logic did not cause sci. 1 = set by hardware when the tco logic or thermal sensor logic causes an sci. 5 usb5_sts ? r/wc. software clears this bit by writing a 1 to it. 0 = usb uhci controller 5 does not need to cause a wake. 1 = set by hardware when usb uhci contro ller 5 needs to cause a wake. wake event will be generated if the corresponding usb2_en bit is set. 4 usb2_sts ? r/wc. software clears this bit by writing a 1 to it. 0 = usb uhci controller 2 does not need to cause a wake. 1 = set by hardware when usb uhci contro ller 2 needs to cause a wake. wake event will be generated if the corresponding usb2_en bit is set. 3 usb1_sts ? r/wc. software clears this bit by writing a 1 to it. 0 = usb uhci controller 1 does not need to cause a wake. 1 = set by hardware when usb uhci contro ller 1 needs to cause a wake. wake event will be generated if the corresponding usb1_en bit is set. 2 swgpe_sts ? r/wc. the swgpe_ctrl bit (bit 1 of gpe_ctrl re g) acts as a level input to this bit. 1 hot_plug_sts ? r/wc. 0 = this bit is cleared by writ ing a 1 to this bit position. 1 = when a pci express* hot-plug event oc curs. this will cause an sci if the hot_plug_en bit is set in the gep0_en register. 0 thermal interrupt status (thrm_sts) ? r/wc. software clears this bit by writing a 1 to it. 0 = thrm# signal not driven active as defined by the thrm_pol bit 1 = set by hardware anytime the thrm# sign al is driven active as defined by the thrm_pol bit. additionally, if the thrm_en bit is set, then the setting of the thrm_sts bit will also generate a po wer management event (sci or smi#). bit description http://www..net/ datasheet pdf - http://www..net/ datasheet 473 lpc interface bridge registers (d31:f0) 13.8.3.10 gpe0_en?general purpose event 0 enables register i/o address: pmbase + 28h ( acpi gpe0_blk + 8 ) attribute: bits 0:32 r/w bits 33:63 ro default value: 0000000000000000h size: 64-bit lockable: no usage: acpi power well: bits 0?7, 9, 12, 14?63 resume, bits 8, 10?11, 13 rtc this register is symmetrical to the general purpose event 0 status register. all the bits in this register should be cleared to 0 based on a power button override or processor thermal trip event. the resume well bits are all cleared by rsmrst#. the rtc well bits are cleared by rtcrst#. bit description 63:33 reserved. 32 usb6_en ? r/w. 0 = disable. 1 = enable the setting of the usb4_sts bit to generate a wake event. the usb6_sts bit is set anytime usb uhci controller #6 signals a wake event. break events are handled via the usb interrupt. 31:16 gpin_en ? r/w. these bits enable the corresp onding gpi[n]_sts bits being set to cause a sci, and/or wake event. these bits are cleared by rsmrst#. note: mapping is as follows: bit 31 corre sponds to gpio15. .. and bit 16 corresponds to gpio0. 15 reserved 14 usb4_en ? r/w. 0 = disable. 1 = enable the setting of the usb4_sts bit to generate a wake event. the usb4_sts bit is set anytime usb uhci controller #4 signals a wake event. break events are handled via the usb interrupt. 13 pme_b0_en ? r/w. 0 = disable 1 = enables the setting of the pme_b0_sts bit to generate a wake event and/or an sci or smi#. pme_b0_sts can be a wake event from the s1?s4 states, or from s5 (if entered via slp_typ and slp_en) or power failure, but not power button override. this bit de faults to 0. note: it is only cleared by software or rtcr st#. it is not clea red by cf9h writes. 12 usb3_en ? r/w. 0 = disable. 1 = enable the setting of the usb3_sts bit to generate a wake event. the usb3_sts bit is set anytime usb uhci controller #3 signals a wake event. break events are handled via the usb interrupt. 11 pme_en ? r/w. 0 = disable. 1 = enables the setting of the pme_sts to generate a wake event and/or an sci. pme# can be a wake event from the s1 ? s4 state or from s5 (if entered via slp_en, but not power button override). 10 reserved http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 474 datasheet 9 pci_exp_en ? r/w. 0 = disable sci generation upon pci_exp_sts bit being set. 1 = enables ich10 to cause an sci when pc i_exp_sts bit is set. this is used to allow the pci express* ports, including th e link to the (g)mch, to cause an sci due to wake/pme events. 8 ri_en ? r/w. the value of this bit will be maintained through a g3 state and is not affected by a hard reset caused by a cf9h write. 0 = disable. 1 = enables the setting of the ri_sts to generate a wake event. 7 reserved 6 tcosci_en ? r/w. 0 = disable. 1 = enables the setting of the tc osci_sts to generate an sci. 5 usb5_en ? r/w. 0 = disable. 1 = enables the setting of the usb5_sts to generate a wake event. 4 usb2_en ? r/w. 0 = disable. 1 = enables the setting of the usb2_sts to generate a wake event. 3 usb1_en ? r/w. 0 = disable. 1 = enables the setting of the usb1_sts to generate a wake event. 2 swgpe_en ? r/w. this bit allows software to control the assertion of swgpe_sts bit. this bit this bit, when set to 1, enables the sw gpe function. if swgpe_ctrl is written to a 1, hardware will se t swgpe_sts (acts as a level input) if swgpe_sts, swgpe_en, and sci_en ar e all 1s, an sci wi ll be generated. if swgpe_sts = 1, swgpe_en = 1, sci_en = 0, and gbl_smi_en = 1 then an smi# will be generated. 1 hot_plug_en ? r/w. 0 = disables sci generation upon the hot_plug_sts bit being set. 1 = enables the ich10 to cause an sci when the hot_plug_sts bit is set. this is used to allow the pci express ports to cause an sci due to hot-plug events. 0 thrm_en ? r/w. 0 = disable. 1 = active assertion of the thrm# signal (as defined by the thrm_pol bit) will generate a power management event (sci or smi) if the thrm_sts bit is also set. bit description http://www..net/ datasheet pdf - http://www..net/ datasheet 475 lpc interface bridge registers (d31:f0) 13.8.3.11 smi_en?smi control and enable register i/o address: pmbase + 30h attribute: r/w, r/wo, wo default value: 00000000h (consumer) size: 32 bit default value: 00000002h (corporate) lockable: no usage: acpi or legacy power well: core note: this register is symmetrical to the smi status register. bit description 31:28 reserved 27 gpio_unlock_smi_en ? r/wo. setting this bit will cause the intel ich10 to generate an smi# when the gpio_unlock_smi_sts bit is set in the smi_sts register. once written to ?1?, this bit can only be cleared by pltrst#. 26:19 reserved 18 intel_usb2_en ? r/w. 0 = disable 1 = enables intel-specific usb2 smi logic to cause smi#. 17 legacy_usb2_en ? r/w. 0 = disable 1 = enables legacy usb2 logic to cause smi#. 16:15 reserved 14 periodic_en ? r/w. 0 = disable. 1 = enables the ich10 to generate an sm i# when the periodic_sts bit (pmbase + 34h, bit 14) is set in the smi_sts register (pmbase + 34h). 13 tco_en ? r/w. 0 = disables tco logic generating an smi#. note that if the nmi2smi_en bit is set, smis that are caused by re-routed nmis wi ll not be gated by th e tco_en bit. even if the tco_en bit is 0, nmis will still be routed to cause smis. 1 = enables the tco logic to generate smi#. note: this bit cannot be written on ce the tco_lock bit is set. 12 reserved 11 mcsmi_enmicrocontroller smi enable (mcsmi_en) ? r/w. 0 = disable. 1 = enables ich10 to trap accesses to th e microcontroller range (62h or 66h) and generate an smi#. note that ?trapped? cycl es will be claimed by the ich10 on pci, but not forwarded to lpc. 10:8 reserved 7 bios release (bios_rls) ? wo. 0 = this bit will always return 0 on reads. writes of 0 to this bit have no effect. 1 = enables the generation of an sci interrup t for acpi software when a one is written to this bit position by bios software. note: gbl_sts being set will caus e an sci, even if the sci_en bit is not set. software must take great care not to set the bios_rls bit (which causes gbl_sts to be set) if the sci handler is not in place. http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 476 datasheet 6 software smi# timer enable (swsmi_tmr_en) ? r/w. 0 = disable. clearing the swsmi_tmr_en bit before the timer expires will reset the timer and the smi# will not be generated. 1 = starts software smi# timer. when the swsmi timer expires (t he timeout period depends upon the swsmi_rate_sel bit se tting), swsmi_tmr_sts is set and an smi# is generated. swsm i_tmr_en stays set until cleared by software. 5 apmc_en ? r/w. 0 = disable. writes to the apm_cnt register will not cause an smi#. 1 = enables writes to the apm_cn t register to cause an smi#. 4 slp_smi_en ? r/w. 0 = disables the generation of smi# on slp_ en. note that this bi t must be 0 before the software attempts to transition the sy stem into a sleep state by writing a 1 to the slp_en bit. 1 = a write of 1 to the slp_en bit (bit 13 in pm1_cnt register) will generate an smi#, and the system will not transition to the sleep state based on that write to the slp_en bit. 3 legacy_usb_en ? r/w. 0 = disable. 1 = enables legacy usb circuit to cause smi#. 2 bios_en ? r/w. 0 = disable. 1 = enables the generation of smi# when acpi software writes a 1 to the gbl_rls bit (d31:f0:pmbase + 04h:bit 2). note that if the bios_sts bit (d31:f0:pmbase + 34h:bit 2), which gets set when software writes 1 to gbl_rls bit, is already a 1 at the time that bios_en becomes 1, an smi# will be generated when bios_en gets set. 1 end of smi (eos) ? r/w (special). this bi t controls the arbitration of the smi signal to the processor. this bit must be set for the ich10 to assert smi# low to the processor after smi# has been asserted previously. 0 = once the ich10 asserts smi# low, the eos bit is automatically cleared. 1 = when this bit is set to 1, smi# signal wi ll be deasserted for 4 pci clocks before its assertion. in th e smi handler, the processor should clear all pending smis (by servicing them and then clearing their resp ective status bits), set the eos bit, and exit smm. this will allow the smi arbiter to re-assert smi upon detection of an smi event and the setting of a smi status bit. note: ich10 is able to generate 1st smi after reset even though eos bit is not set. subsequent smi require eos bit is set. 0 gbl_smi_en ? r/w. 0 = no smi# will be generated by ich10. this bit is reset by a pci reset event. 1 = enables the generation of smi# in the system upon any enabled smi event. note: when the smi_lock bit is set, this bit cannot be changed. bit description http://www..net/ datasheet pdf - http://www..net/ datasheet 477 lpc interface bridge registers (d31:f0) 13.8.3.12 smi_sts?smi status register i/o address: pmbase + 34h attribute: ro, r/wc default value: 00000000h size: 32-bit lockable: no usage: acpi or legacy power well: core note: if the corresponding _en bit is set when th e _sts bit is set, the ich10 will cause an smi# (except bits 8?10 and 12, which do not need enable bits since they are logic ors of other registers that have enable bits). the ich10 uses the same gpe0_en register (i/o address: pmbase+2ch) to enable/disab le both smi and acpi sci general purpose input events. acpi os assumes that it owns the entire gpe0_en register per acpi spec. problems arise when some of the general-pu rpose inputs are enabled as smi by bios, and some of the general purpose inputs are en abled for sci. in this case acpi os turns off the enabled bit for any gpix input sign als that are not indicated as sci general- purpose events at boot, and exit from slee ping states. bios should define a dummy control method which prevents the acpi os from clearing the smi gpe0_en bits. bit description 31:28 reserved 27 gpio_unlock_smi_sts ? r/wc. this bit will be set if the gpio registers lockdown logic is requesting an smi#. writing a 1 to this bit position clears this bit to 0. 26 spi_sts ? ro. this bit will be set if the spi logic is generating an smi#. this bit is read only because the sticky st atus and enable bits associat ed with this function are located in the spi registers. 25:22 reserved 21 monitor_sts ? ro. this bit will be set if the trap/smi logic has caused the smi. this will occur when the processor or a bus master accesses an assigned register (or a sequence of accesses). see section 10.1.43 through section 10.1.49 for details on the specific cause of the smi. 20 pci_exp_smi_sts ? ro. pci express* smi event occurre d. this could be due to a pci express pme event or hot-plug event. 19 reserved 18 intel_usb2_sts ? ro. this non-sticky read-only bit is a logical or of each of the smi status bits in the intel-specific us b2 smi status register anded with the corresponding enable bits. additionally, the po rt disable write enable smi is reported in this bit; the specific status bit for this event is contained in the usb per-port registers write control register in this i/o space. this bit will not be active if the enable bits are not set. writes to this bit will have no effect. all integrated usb2 host controll ers are represented with this bit. 17 legacy_usb2_sts ? ro. this non-sticky read-only bit is a logical or of each of the smi status bits in the usb2 legacy suppo rt register anded with the corresponding enable bits. this bit will not be active if the enable bits are not set. writes to this bit will have no effect. all integrated usb2 host controll ers are represented with this bit. http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 478 datasheet 16 smbus smi status (smbus_smi_sts) ? r/wc. software clears this bit by writing a 1 to it. 0 = this bit is set from the 64 khz clock do main used by the sm bus. software must wait at least 15.63 s after the initial assertion of this bit before clearing it. 1 = indicates that the smi# was caused by: 1. the smbus slave receiving a message that an smi# should be caused, or 2. the smbalert# signal goes active and the smb_smi_en bit is set and the smbalert_dis bit is cleared, or 3. the smbus slave receiving a host notify message and the host_notify_intren and the smb_smi_en bits are set, or 4. the ich10 detecting the smlink_slave _smi command while in the s0 state. 15 serirq_smi_sts ? ro. 0 = smi# was not caused by the serirq decoder. 1 = indicates that the smi# was caused by the serirq decoder. note: this is not a sticky bit 14 periodic_sts ? r/wc. software clears this bit by writing a 1 to it. 0 = software clears this bit by writing a 1 to it. 1 = this bit is set at the rate determined by the per_smi_sel bits. if the periodic_en bit (pmbase + 30h, bit 14) is also set, the ich10 generates an smi#. 13 tco_sts ? r/wc. software clears this bit by writing a 1 to it. 0 = smi# not caused by tco logic. 1 = indicates the smi# was caused by the tco logic. note that this is not a wake event. 12 device monitor status (devmon_sts) ? ro. 0 = smi# not caused by device monitor. 1 = set if bit 0 of the devact_sts register (pmbase + 44h) is set. the bit is not sticky, so writes to this bit will have no effect. 11 microcontroller smi# status ( mcsmi_sts) ? r/wc. software clears this bit by writing a 1 to it. 0 = indicates that there has been no access to the power management microcontroller range (62h or 66h). 1 = set if there has been an access to the power management microcontroller range (62h or 66h) and the microcontroller deco de enable #1 bit in the lpc bridge i/o enables configuration register is 1 (d31 :f0:offset 82h:bit 11). note that this implementation assumes that the microcontroller is on lpc. if this bit is set, and the mcsmi_en bit is also set, the ich10 will generate an smi#. 10 gpe0_sts ? ro. this bit is a logical or of the bi ts in the alt_gp_smi_sts register that are also set up to cause an smi# (a s indicated by the gpi_rout registers) and have the corresponding bit set in the alt_ gp_smi_en register. bits that are not routed to cause an smi# will have no effect on this bit. 0 = smi# was not generated by a gpi assertion. 1 = smi# was generated by a gpi assertion. 9 gpe0_sts ? ro. this bit is a logical or of the bits 47:32, 14:10, 8, 6:2 and 0 in the gpe0_sts register (pmbase + 28h) that also have the co rresponding bit set in the gpe0_en register (pmbase + 2ch). 0 = smi# was not generated by a gpe0 event. 1 = smi# was generated by a gpe0 event. bit description http://www..net/ datasheet pdf - http://www..net/ datasheet 479 lpc interface bridge registers (d31:f0) 13.8.3.13 alt_gp_smi_en?alterna te gpi smi enable register i/o address: pmbase +38h attribute: r/w default value: 0000h size: 16-bit lockable: no usage: acpi or legacy power well: resume 8 pm1_sts_reg ? ro. this is an ors of the bits in the acpi pm1 status register (offset pmbase+00h) that can cause an smi#. 0 = smi# was not generated by a pm1_sts event. 1 = smi# was generated by a pm1_sts event. 7 reserved 6 swsmi_tmr_sts ? r/wc. software clears this bit by writing a 1 to it. 0 = software smi# timer has not expired. 1 = set by the hardware when th e software smi# timer expires. 5 apm_sts ? r/wc. software clears this bit by writing a 1 to it. 0 = no smi# generated by writ e access to apm control register with apmch_en bit set. 1 = smi# was generated by a write access to the apm control register with the apmc_en bit set. 4 slp_smi_sts ? r/wc. software clears this bit by writing a 1 to the bit location. 0 = no smi# caused by write of 1 to slp_ en bit when slp_smi_en bit is also set. 1 = indicates an smi# was caused by a write of 1 to slp_en bit when slp_smi_en bit is also set. 3 legacy_usb_sts ? ro. this bit is a logical or of each of the smi status bits in the usb legacy keyboard/mouse control regist ers anded with the corresponding enable bits. this bit will not be active if the enable bits are not set. 0 = smi# was not generated by usb legacy event. 1 = smi# was generated by usb legacy event. 2 bios_sts ? r/wc. 0 = no smi# generated due to acpi software requesti ng attention. 1 = this bit gets set by hardware when a 1 is written by software to the gbl_rls bit (d31:f0:pmbase + 04h:bit 2). when bo th the bios_en bit (d31:f0:pmbase + 30h:bit 2) and the bios_sts bit are se t, an smi# will be generated. the bios_sts bit is cleared when softwa re writes a 1 to its bit position. 1:0 reserved bit description bit description 15:0 alternate gpi smi enable ? r/w. these bits are used to enable the corresponding gpio to cause an smi#. for th ese bits to have any effect, the following must be true. ? the corresponding bit in the alt_gp_smi_en register is set. ? the corresponding gpi must be routed in the gpi_rout register to cause an smi. ? the corresponding gpio must be implemented. note: mapping is as follows: bit 15 correspon ds to gpio15... bit 0 corresponds to gpio0. http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 480 datasheet 13.8.3.14 alt_gp_smi_sts?altern ate gpi smi status register i/o address: pmbase +3ah attribute: r/wc default value: 0000h size: 16-bit lockable: no usage: acpi or legacy power well: resume 13.8.3.15 uprwc?usb per-port registers write control i/o address: pmbase +3ch attribute: r/wc, r/w, r/wo default value: 0000h size: 16-bit lockable: no usage: acpi or legacy power well: resume bit description 15:0 alternate gpi smi status ? r/wc. these bits report th e status of the corresponding gpios. 0 = inactive. software clears th is bit by writing a 1 to it. 1 = active these bits are sticky. if the following conditions are true, then an smi# will be generated and the gpe0_sts bit set: ? the corresponding bit in the alt_gpi_sm i_en register (pmbase + 38h) is set ? the corresponding gpio must be routed in the gpi_rout register to cause an smi. ? the corresponding gpio must be implemented. all bits are in the resume well. default for these bits is dependent on the state of the gpio pins. bit description 15:9 reserved 8 write enable status ? r/wc 0 = this bit gets set by hardware when the ?per-port registers write enable? bit is written from 0-to-1. 1 = this bit is cleared by software writing a 1b to this bit location the setting condition takes precedence over the clearing condition in the event that both occur at once. when this bit is 1b and bit 0 is 1b, the intel_usb2_sts bit is set in the smi_sts register. 7:2 reserved. 1 reserved 0 write enable smi enable ? r/wo 0 = disable 1 = enables the generation of smi when the pe r-port registers write enable (bit 1) is written from 0 to 1. once written to 1b, this bit can not be cleared by software. http://www..net/ datasheet pdf - http://www..net/ datasheet 481 lpc interface bridge registers (d31:f0) 13.8.3.16 gpe_cntl? general purpose control register i/o address: pmbase +42h attribute: r/w default value: 00h size: 8-bit lockable: no usage: acpi or legacy power well: resume 13.8.3.17 devact_sts ? device activity status register i/o address: pmbase +44h attribute: r/wc default value: 0000h size: 16-bit lockable: no usage: legacy only power well: core each bit indicates if an access has occurred to the corresponding device?s trap range, or for bits 6:9 if the corresponding pci interru pt is active. this register is used in conjunction with the periodic smi# timer to detect any system activity for legacy power management. the periodic smi# timer indicates if it is the right time to read the devact_sts register (pmbase + 44h). note: software clears bits that are set in this register by writing a 1 to the bit position. bit description 8:2 reserved 1 swgpe_ctrl ? r/w. this bit allows software to control the assertion of swgpe_sts bit. this bit is used by hardware as the level input signal for the swgpe_sts bit in the gpe0_sts register. when swgpe_ctrl is 1, sw gpe_sts will be set to 1, and writes to swgpe_sts with a value of 1 to clear swgpe_sts will result in swgpe_sts being set back to 1 by hardware. when swgpe_ctrl is 0, writes to swgpe_sts with a value of 1 will clear swgpe_sts to 0. 0 thrm#_pol ? r/w. this bit controls the polarity of the thrm# pin needed to set the thrm_sts bit. 0 = low value on the thrm# signal will set the thrm_sts bit. 1 = high value on the thrm# signal will set the thrm_sts bit. bit description 15:13 reserved 12 kbc_act_sts ? r/wc. kbc (60/64h). 0 = indicates that there has been no access to this device?s i/o range. 1 = this device?s i/o range has been accessed . clear this bit by wr iting a 1 to the bit location. 11:10 reserved 9 pirqdh_act_sts ? r/wc. pirq[d or h]. 0 = the corresponding pci interrupts have not been active. 1 = at least one of the corresponding pci inte rrupts has been active . clear this bit by writing a 1 to the bit location. 8 pirqcg_act_sts ? r/wc. pirq[c or g]. 0 = the corresponding pci interrupts have not been active. 1 = at least one of the corresponding pci inte rrupts has been active . clear this bit by writing a 1 to the bit location. http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 482 datasheet 13.8.3.18 pm2_cnt?power management 2 control i/o address: pmbase + 50h (acpi pm2_cnt_blk) attribute: r/w default value: 00h size: 8-bit lockable: no usage: acpi power well: core 13.8.3.19 c3_res? c3 residency register i/o address: pmbase +54h attribute: ro default value 00000000h size: 32-bit lockable: no usage: acpi/legacy power well: core software may only write this register during system initialization to set the state of the c3_residency_mode bit. it must not be written while the timer is in use. 7 pirqbf_act_sts ? r/wc. pirq[b or f]. 0 = the corresponding pci inte rrupts have not been active. 1 = at least one of the corresponding pci inte rrupts has been active . clear this bit by writing a 1 to the bit location. 6 pirqae_act_sts ? r/wc. pirq[a or e]. 0 = the corresponding pci inte rrupts have not been active. 1 = at least one of the corresponding pci inte rrupts has been active . clear this bit by writing a 1 to the bit location. 5:0 reserved bit description bit description 7:1 reserved 0 arbiter disable (arb_dis) ? r/w this bit is essentially just a scratchpad bit for legacy software compatibility. software typicall y sets this bit to 1 prior to entering a c3 or c4 state. when a transition to a c3 or c4 state occurs, ich 10 will automatically prevent any internal or external non-isoch bu s masters from initiating any cycles up to the (g)mch. this blocking starts immediately upon the ich10 sending the go-c3 message to the (g)mch. the blocking stops when the ack-c2 message is received. note that this is not really blocking, in that messages (such as from pci express*) are just queued and held pending. bit description 31:24 reserved 23:0 c3_residency ? ro. the value in this field incr ements at the same rate as the power management timer. this field increments while stp_cpu# is active (i.e., the processor is in a c3 or c4 st ate). this field will roll over in the same way as the pm timer, however the most significant bit is not sticky. software is responsible for reading this fi eld before performing th e lvl3/4 transition. software must also check for rollover if the maximum time in c3/c4 could be exceeded. note: hardware reset is the only reset of this counter field. http://www..net/ datasheet pdf - http://www..net/ datasheet 483 lpc interface bridge registers (d31:f0) 13.9 system management tco registers (d31:f0) the tco logic is accessed via registers mapped to the pci configuration space (device 31:function 0) and the system i/o space. for tco pci configuration registers, see lpc device 31:function 0 pci configuration registers. tco register i/o map the tco i/o registers reside in a 32-byte range pointed to by a tcobase value, which is, pmbase + 60h in the pci config space. the following table shows the mapping of the registers within that 32-byte range. each register is described in the following sections. 13.9.1 tco_rld?tco timer reload and current value register i/o address: tcobase +00h attribute: r/w default value: 0000h size: 16-bit lockable: no power well: core table 13-12. tco i/o register address map tcobase + offset mnemonic register name default type 00h?01h tco_rld tco timer reload and current value 0000h r/w 02h tco_dat_in tco data in 00h r/w 03h tco_dat_out tco data out 00h r/w 04h?05h tco1_sts tco1 status 0000h r/wc, ro 06h?07h tco2_sts tco2 status 0000h r/wc 08h?09h tco1_cnt tco1 control 0000h r/w, r/wlo, r/wc 0ah?0bh tco2_cnt tco2 control 0008h r/w 0ch?0dh tco_message1, tco_message2 tco message 1 and 2 00h r/w 0eh tco_wdcnt watchdog control 00h r/w 0fh ? reserved ? ? 10h sw_irq_gen software irq generation 03h r/w 11h ? reserved ? ? 12h?13h tco_tmr tco timer initial value 0004h r/w 14h?1fh ? reserved ? ? bit description 15:10 reserved 9:0 tco timer value ? r/w. reading this register will return the current count of the tco timer. writing any value to this register will reload the timer to prevent the timeout. http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 484 datasheet 13.9.2 tco_dat_in?tco data in register i/o address: tcobase +02h attribute: r/w default value: 00h size: 8-bit lockable: no power well: core 13.9.3 tco_dat_out?tco data out register i/o address: tcobase +03h attribute: r/w default value: 00h size: 8-bit lockable: no power well: core 13.9.4 tco1_sts?tco1 status register i/o address: tcobase +04h attribute: r/wc, ro default value: 0000h (consumer only) size: 16-bit 2000h (corporate only) lockable: no power well: core (except bit 7, in rtc) bit description 7:0 tco data in value ? r/w. this data register field is used for pass ing commands from the os to the smi handler. writes to this register will caus e an smi and set the sw_tco_smi bit in the tco1_sts register (d31:f0:04h). bit description 7:0 tco data out value ? r/w. this data register fiel d is used for passing commands from the smi handler to the os. writes to this register will set the tco_int_sts bit in the tco_sts register. it will also cause an interrupt, as selected by the tco_int_sel bits. bit description 15:14 reserved 13 (corporate only) tco_slvsel (tco slave select) - ro. this register bit is re ad only by host and indicates the value of tco slave select so ft strap. refer to the ich soft straps section of the spi chapter for details. 13 (consumer only) reserved 12 dmiserr_sts ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = ich10 received a dmi special cycle message via dmi indicating that it wants to cause an serr#. the software must read the (g)mch to determine the reason for the serr#. 11 reserved 10 dmismi_sts ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = ich10 received a dmi special cycle message via dmi indicating that it wants to cause an smi. the software must read the (g)mch to determine the reason for the smi. http://www..net/ datasheet pdf - http://www..net/ datasheet 485 lpc interface bridge registers (d31:f0) 9 dmisci_sts ? r/wc. 0 = software clears this bi t by writing a 1 to it. 1 = ich10 received a dmi special cycle messag e via dmi indicating that it wants to cause an sci. the software must read the (g)mch to determ ine the reason for the sci. 8 bioswr_sts ? r/wc. 0 = software clears this bi t by writing a 1 to it. 1 = ich10 sets this bit and ge nerates and smi# to indicate an invalid attempt to write to the bios. this occurs when either: a) the bioswp bit is changed from 0 to 1 and the bld bit is also set, or b) any write is attempted to the bios and the bioswp bit is also set. note: on write cycles attempted to the 4 mb lower alias to the bios space, the bioswr_sts will not be set. 7 newcentury_sts ? r/wc. this bit is in the rtc well. 0 = cleared by writing a 1 to the bit position or by rtcrst# going active. 1 = this bit is set when the year byte (rtc i/o space, index offset 09h) rolls over from 99 to 00. setting this bit will ca use an smi# (but not a wake event). note: the newcentury_sts bit is not vali d when the rtc battery is first installed (or when rtc power has no t been maintained). software can determine if rtc power has not be en maintained by checking the rtc_pwr_sts bit (d31:f0:a4h, bit 2), or by other means (such as a checksum on rtc ram). if rtc power is determined to have not been maintained, bios should set the time to a valid value and then clear the newcentury_sts bit. the newcentury_sts bit may take up to 3 rtc clocks for the bit to be cleared after a 1 is written to the bit to clear it. after writing a 1 to this bit, software should not exit the smi handler until verifying that the bit has actually been cleared. this will ensure that the smi is not re-entered. 6:4 reserved 3 timeout ? r/wc. 0 = software clears this bi t by writing a 1 to it. 1 = set by ich10 to indicate that the smi was caused by the tco timer reaching 0. 2 tco_int_sts ? r/wc. 0 = software clears this bi t by writing a 1 to it. 1 = smi handler caused the interrupt by writing to the tco_dat_out register (tcobase + 03h). 1 sw_tco_smi ? r/wc. 0 = software clears this bi t by writing a 1 to it. 1 = software caused an smi# by writing to the tco_dat_in register (tcobase + 02h). 0 nmi2smi_sts ? ro. 0 = cleared by clearing the associated nmi status bit. 1 = set by the ich10 when an smi# occurs because an event occurred that would otherwise have caused an nmi (because nmi2smi_en is set). bit description http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 486 datasheet 13.9.5 tco2_sts?tco2 status register i/o address: tcobase +06h attribute: r/wc default value: 0000h size: 16-bit lockable: no power well: resume (except bit 0, in rtc) bit description 15:8 reserved 7:5 (corporate only) reserved 7 (consumer only) me host reset warm status (me_hrst_warm_sts) ? r/wc. this bit is set when the intel management engine genera tes a host reset without power cycling. software clears this bit by wr iting a 1 to this bit position. 6 (consumer only) me host reset cold status (me_hrst_cold_sts) ? r/wc. this bit is set when the intel management engine generates a host reset with power cycling. software clears this bit by wr iting a 1 to this bit position. 5 (consumer only) me wake status (me_wake_sts) ? r/wc. this bit is set when the intel management engine generates a non-maskable wake event, and is not affected by any other enable bit. when this bit is set, the host power management logic wakes to s0. this bit is only set by hardware and can on ly be reset by writin g a one to this bit position. this bit is not affect ed by hard resets caused by a cf9h write, but is reset by rsmrst. 4 smlink slave smi status (smlink_slv_smi_sts) ? r/wc. allow the software to go directly into pre-dete rmined sleep state. this avoids race conditions. software clears this bit by writing a 1 to it. 0 = the bit is reset by rsmr st#, but not due to the pci reset associated with exit from s3?s5 states. 1 = ich10 sets this bit to 1 when it receives the smi message on the smlink's slave interface. 3 reserved. 2 boot_sts ? r/wc. 0 = cleared by ich10 based on rsmrst# or by software writing a 1 to this bit. note that software should first clear the second_to_sts bit before writing a 1 to clear the boot_sts bit. 1 = set to 1 when the second_to_sts bi t goes from 0 to 1 and the processor has not fetched the first instruction. if rebooting due to a second tco timer timeout, and if the boot_sts bit is set, the ich10 will reboot using the ?safe? multiplier (1111). this allows the system to recover from a processor frequen cy multiplier that is too high, and allows the bios to check the boot_sts bit at boot. if the bit is set and the frequency multiplier is 1111, then the bios knows that the processor has been programmed to an invalid multiplier. 1 second_to_sts ? r/wc. 0 = software clears this bit by wr iting a 1 to it, or by a rsmrst#. 1 = ich10 sets this bit to 1 to indicate that the timeout bit had been (or is currently) set and a second timeout oc curred before the tco_rld register was written. if this bit is set and the no_reboot config bit is 0, then the ich10 will reboot the system after the second timeout. the reboot is done by asserting pltrst#. http://www..net/ datasheet pdf - http://www..net/ datasheet 487 lpc interface bridge registers (d31:f0) 0 intruder detect (intrd_det) ? r/wc. 0 = software clears this bit by writing a 1 to it, or by rtcrst# assertion. 1 = set by ich10 to indicate that an intrusion was detected. this bit is set even if the system is in g3 state. notes: 1. this bit has a recovery time. after writin g a 1 to this bit position (to clear it), the bit may be read back as a 1 for up 65 microseconds before it is read as a 0. software must be aware of this recove ry time when reading this bit after clearing it. 2. if the intruder# signal is active wh en the software attempts to clear the intrd_det bit, the bit will remain as a 1, and the smi# will be generated again immediately. the sm i handler can clear the intrd_sel bits (tcobase + 0ah, bits 2:1), to avoid further smis. however, if the intr uder# signals goes inactive and then active again, there will not be further smi?s (because the intrd_sel bits would select that no sm i# be generated). 3. if the intruder# signal goes inactive some point after the intrd_det bit is written as a 1, then the intrd_det si gnal will go to a 0 when intruder# input signal goes inactive. note that this is slightly different than a classic sticky bit, since most sticky bits woul d remain active inde finitely when the signal goes active and woul d immediately go inactive when a 1 is written to the bit description http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 488 datasheet 13.9.6 tco1_cnt?tco1 control register i/o address: tcobase +08h a ttribute: r/w, r/wlo, r/wc default value: 0000h size: 16-bit lockable: no power well: core bit description 15:13 reserved 12 tco_lock ? r/wlo. when set to 1, this bi t prevents writes from changing the tco_en bit (in offset 30h of power management i/o space). once this bit is set to 1, it can not be cleared by software writing a 0 to this bit location. a core-well reset is required to change this bit from 1 to 0. this bit defaults to 0. 11 tco timer halt (tco_tmr_hlt) ? r/w. 0 = the tco timer is enabled to count. 1 = the tco timer will halt. it will not count, and thus cannot reach a value that will cause an smi# or set the second_to_sts bit. when set, this bit will prevent rebooting and prevent alert on lan even t messages from being transmitted on the smlink (but not alert on lan* heartbeat messages). 10 reserved 9 nmi2smi_en ? r/w. 0 = normal nmi functionality. 1 = forces all nmis to instead cause smis. th e functionality of this bit is dependent upon the settings of the nmi_en bit and the gbl_smi_en bit as detailed in the following table: 8 nmi_now ? r/wc. 0 = software clears this bit by writing a 1 to it. the nmi handler is expected to clear this bit. another nmi will not be generated until the bit is cleared. 1 = writing a 1 to this bit causes an nmi. this allows the bios or smi handler to force an entry to the nmi handler. 7:0 reserved nmi_en gbl_smi_en description 0b 0b no smi# at all because gbl_smi_en = 0 0b 1b smi# will be caused due to nmi events 1b 0b no smi# at all because gbl_smi_en = 0 1b 1b no smi# due to nmi because nmi_en = 1 http://www..net/ datasheet pdf - http://www..net/ datasheet 489 lpc interface bridge registers (d31:f0) 13.9.7 tco2_cnt?tco2 control register i/o address: tcobase +0ah attribute: r/w default value: 0008h size: 16-bit lockable: no power well: resume 13.9.8 tco_message1 and tc o_message2 registers i/o address: tcobase +0ch (message 1)attribute: r/w tcobase +0dh (message 2) default value: 00h size: 8-bit lockable: no power well: resume bit description 15:6 reserved 5:4 os_policy ? r/w. os-based software writes to these bits to select the policy that the bios will use after the pl atform resets due the wdt. the following convention is recommended for the bios and os: 00 = boot normally 01 = shut down 10 = don?t load os. hold in pre-boot state and use lan to determine next step 11 = reserved note: these are just scratchpad bits. they should not be reset when the tco logic resets the platform due to watchdog timer. 3 gpio11_alert_disable ? r/w. at reset (via rsmrst# asserted) this bit is set and gpio[11] alerts are disabled. 0 = enable. 1 = disable gpio11/smbalert# as an alert source for the heartbeats and the smbus slave. 2:1 intrd_sel ? r/w. this field selects the action to take if the intruder# signal goes active. 00 = no interrupt or smi# 01 = interrupt (as sele cted by tco_int_sel). 10 = smi 11 = reserved 0 reserved bit description 7:0 tco_message[ n ] ? r/w. bios can write into these registers to indicate its boot progress. the external microc ontroller can read these registers to monitor the boot progress http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 490 datasheet 13.9.9 tco_wdcnt?tco watc hdog control register offset address: tcobase + 0eh attribute: r/w default value: 00h size: 8 bits power well: resume 13.9.10 sw_irq_gen?software irq generation register offset address: tcobase + 10h attribute: r/w default value: 03h size: 8 bits power well: core 13.9.11 tco_tmr?tco timer initial value register i/o address: tcobase +12h attribute: r/w default value: 0004h size: 16-bit lockable: no power well: core bit description 7:0 the bios or system management software can write into this register to indicate more details on the boot progress. the register will reset to 00h based on a rsmrst# (but not pltrst#). the external microcontroller can read this register to monitor boot progress. bit description 7:2 reserved 1 irq12_cause ? r/w. when software sets this bit to 1, irq12 will be asserted. when software sets this bit to 0, irq12 will be deasserted. 0 irq1_cause ? r/w. when software sets this bit to 1, irq1 will be asserted. when software sets this bit to 0, irq1 will be deasserted. bit description 15:10 reserved 9:0 tco timer initial value ? r/w. value that is loaded into the timer each time the tco_rld register is written. values of 0000h or 0001h will be ignored and should not be attempted. the timer is clocked at a pproximately 0.6 seconds, and thus allows timeouts ranging from 1.2 second to 613.8 s econds. note: the ti mer has an error of 1 tick (0.6s). the tco timer will only count down in the s0 state. http://www..net/ datasheet pdf - http://www..net/ datasheet 491 lpc interface bridge registers (d31:f0) 13.10 general purpose i/o registers (d31:f0) the control for the general purpose i/o sign als is handled through a separate 64-byte i/o space (consumer only) and 128-byte i/o space (corporate only). the base offset for this space is selected by the gpiobase register. table 13-13. registers to control gpio address map gpiobase + offset mnemonic register name default access 00h?03h gpio_use_sel gpio use select 197f75ffh r/w 04h?07h gp_io_sel gpio input/ output select e0ea6fffh r/w 08h?0bh ? reserved ? ? 0ch?0fh gp_lvl gpio level for input or output e2feefffh r/w 10h?13h ? reserved ? ? 14h?17h ? reserved ? ? 18h?1bh gpo_blink gpio blink enable 00040000h r/w 1ch?1fh gp_ser_blink gp serial blink 00000000h r/w 20?23h gp_sb_cmdsts gp serial blink command status 00080000h r/w 24?27h gp_sb_data gp serial blink data 00000000h r/w 28?2bh reserved 2c?2fh gpi_inv gpio signal invert 00000000h r/w 30h?33h gpio_use_sel2 gpio use select 2 070300ffh r/w 34h?37h gp_io_sel2 gpio input/output select 2 1b55fff0h r/w 38h?3bh gp_lvl2 gpio level for input or output 2 1ffefff3h r/w 3ch?3fh ? reserved ? ? 40h?43h (corporate only) gpio_use_sel3 gpio use select 3 r/w 44h?47h (corporate only) gpio_sel3 gpio input/output select 3 r/w 48h?4bh (corporate only) gp_lvl3 gpio level for input or output 3 r/w 4ch?5fh (corporate only) ? reserved ? ? 60h?63h gp_rst_sel gpio reset select r/w 64h?7fh (corporate only) ? reserved ? ? http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 492 datasheet 13.10.1 gpio_use_sel?gpio use select register offset address: gpiobase + 00h attribute: r/w default value: 197f75ffh size: 32-bit lockable: yes power well: core for 0:7, 16:23, resume for 8:15, 24:31 13.10.2 gp_io_sel?gpio input/output select register offset address: gpiobase +04h attribute: r/w default value: e0ea6fffh size: 32-bit lockable: yes power well: core for 0:7, 16:23, resume for 8:15, 24:31 bit description 31:0 gpio_use_sel[31:0] ? r/w. each bit in this regi ster enables the corresponding gpio (if it exists) to be used as a gp io, rather than for the native function. 0 = signal used as native function. 1 = signal used as a gpio. notes: 1. the following bits are always 1 because they are always unmultiplexed: 8, 12, 13, 17, 18, 20, 27 and 28. 2. if gpio[n] does not exist, then, the n-bit in this register will always read as 0 and writes will have no effect. 3. after a full reset (rsmrst#) all multip lexed signals in the resume and core wells are configured as their default f unction. after only a pltrst#, the gpios in the core well are configur ed as their default function. 4. when configured to gpio mode, the muxing logic will present the inactive state to native logic that uses the pin as an input. 5. all gpios are reset to the default state by cf9h reset except gpio24. 6. bit 26 may be overridden by bit 8 in the gen_pmcon_3 register. bit description 31:0 gp_io_sel[31:0] ? r/w. when configured in native mode (gpio_use_ sel[n] is 0), writes to these bits have no effect. the value reported in this re gister is undefined when programmed as native mode. 0 = output. the corresponding gpio signal is an output. 1 = input. the corresponding gpio signal is an input. http://www..net/ datasheet pdf - http://www..net/ datasheet 493 lpc interface bridge registers (d31:f0) 13.10.3 gp_lvl?gpio level for input or output register offset address: gpiobase +0ch attribute: r/w default value: e2feefffh size: 32-bit lockable: yes power well: core for 0:7, 16:23, resume for 8:15, 24:31 13.10.4 gpo_blink?gpo b link enable register offset address: gpiobase +18h attribute: r/w default value: 00040000h size: 32-bit lockable: no power well: core for 0:7, 16:23, resume for 8:15, 24:31 note: gpio18 will blink by default imme diately after reset. this signal could be connected to an led to indicate a failed boot (by programmin g bios to clear gp_blink18 after successful post). bit description 31:0 gp_lvl[31:0] ? r/w. if gpio[n] is programmed to be an outp ut (via the corresponding bit in the gp_io_sel register), then the corresponding gp_lvl[n ] bit can be updated by software to drive a high or low value on the output pin. 1 = high, 0 = low. if gpio[n] is programmed as an input, then the corresponding gp_lvl bit reflects the state of the input signal (1 = high, 0 = low.) and writes will have no effect. when configured in native mode (gpio_use_ sel[n] is 0), writes to these bits have no effect. the value reported in this register is unde fined when programmed as native mode. bit description 31:0 gp_blink[31:0] ? r/w. the setting of this bit has no effect if the corresponding gpio signal is programmed as an input. 0 = the corresponding gpio will function normally. 1 = if the corresponding gpio is programmed as an output, the output signal will blink at a rate of approximately once per second. the high and low times have approximately 0.5 seconds each. the gp_lvl bit is not altered when this bit is set. the value of the corresponding gp_lvl bit remains unchanged during the blink process, and does not effect the blink in any way. the gp_lvl bit is not altered when programmed to blink. it wi ll remain at its previous value. these bits correspond to gpio in the resu me well. these bits revert to the default value based on rsmrst# or a write to the cf9h register (but not just on pltrst#). http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 494 datasheet 13.10.5 gp_ser_blink?gp serial blink offset address: gpiobase +1ch attribute: r/w default value: 00000000h size: 32-bit lockable: no power well: core for 0:7, 16:23, resume for 8:15, 24:31 bit description 31:0 gp_ser_blink[31:0] ? r/w. the setting of this bit has no effect if the corresponding gpio is programmed as an input or if the corresponding gpio has the gpo_blink bit set. when set to a ?0?, the correspondi ng gpio will function normally. when using serial blink, this bit should be set to a 1 while the corresponding gp_io_sel bit is set to 1. setting the gp_io_sel bit to 0 after the gp_ser_blink bit ensures ich will not drive a 1 on the pin as an output. when this corresponding bit is set to a 1 and the pin is configured to output mode, the se rial blink capability is enabled. the ich will serialize me ssages through an open-drain buffer configuration. the value of the corresponding gp_lvl bi t remains unchanged and does not impact the serial blink capability in any way. writes to this register have no effect wh en the corresponding pin is configured in native mode and the read va lue returned is undefined. http://www..net/ datasheet pdf - http://www..net/ datasheet 495 lpc interface bridge registers (d31:f0) 13.10.6 gp_sb_cmdsts?gp seri al blink command status offset address: gpiobase +20h attribute: r/w, ro default value: 00000800h size: 32-bit lockable: no power well: core 13.10.7 gp_sb_data?gp serial blink data offset address: gpiobase +24h attribute: r/w default value: 00000000h size: 32-bit lockable: no power well: core bit description 31:24 reserved 23:22 data length select (dls) ? r/w. this field determines the number of bytes to serialize on gpio 00 = serialize bits 7:0 of gp_sb_data (1 byte) 01 = serialize bits 15:0 of gp_sb_data (2 bytes) 10 = undefined - software must not write this value 11 = serialize bits 31:0 of gp_sb_data (4 bytes) software should not modify the value in this register unless the busy bit is clear. writes to this register have no effect when the corresponding pin is configured in native mode and the read va lue returned is undefined. 21:16 data rate select (drs) ? r/w. this field selects the number of 120ns time intervals to count between manchester data transitions. the default of 8h results in a 960ns minimum time between transitions. a value of 0h in this register produces undefined behavior. software should not modify the value in th is register unless th e busy bit is clear. 15:9 reserved 8 busy ? ro. this read-only status bit is the ha rdware indication th at a serialization is in progress. hardware sets this bit to 1 based on the go bit being set. hardware clears this bit when the go bi t is cleared by the hardware. 7:1 reserved 0 go ? r/w. this bit is set to 1 by softwa re to start the serialization process. hardware clears the bit after the serialized da ta is sent. writes of 0 to this register have no effect. softwa re should not write this bit to 1 unless the busy status bit is cleared. bit description 31:0 gp_sb_data[31:0] ? r/w. this register contains the data serialized out. the number of bits shifted out are selected through the dls field in the gp_sb_cmdsts register. this register should not be modifi ed by software when the busy bit is set. http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 496 datasheet 13.10.8 gpi_inv?gpio sign al invert register offset address: gpiobase +2ch attribute: r/w default value: 00000000h size: 32-bit lockable: no power well: cpu i/o for 17, core for 16, 7:0 bit description 31:0 input inversion (gp_inv[n]) ? r/w. this bit only has effect if the corresponding gpio is used as an input and used by the gpe logic, where the polarity matters. when set to ?1?, then the gpi is inverted as it is sent to the gpe logic that is using it. this bit has no effect on the value that is reported in the gp_lvl register. these bits are used to allow both active-low and active-high inputs to cause smi# or sci. note that in the s0 or s1 state, the input signal must be active for at least two pci clocks to ensure detection by the ich10. in the s3, s4 or s5 states the input signal must be active for at least 2 rtc clocks to ensure detectio n. the setting of these bits has no effect if the corresponding gpio is programmed as an output. these bits correspond to gpi that are in the resume well, and will be reset to their default values by rsmrst# or by a write to the cf9h register. 0 = the corresponding gpi_sts bit is set when the ich10 detects the state of the input pin to be high. 1 = the corresponding gpi_sts bit is set when the ich10 detects the state of the input pin to be low. http://www..net/ datasheet pdf - http://www..net/ datasheet 497 lpc interface bridge registers (d31:f0) 13.10.9 gpio_use_sel2?gpio use select 2 register offset address: gpiobase +30h attribute: r/w default value: 070300ffh (consumer only) size: 32-bit tbdh (corporate only) lockable: yes power well: core for 0:7, 16:23, resume for 8:15, 24:31 bit description 31:0 corporate only gpio_use_sel2[63:32] ? r/w. each bit in this register enables the corresponding gpio (if it exis ts) to be used as a gpio, rather than for the native function. 0 = signal used as native function. 1 = signal used as a gpio. notes: 1. the following bit is always 1 because it is always unmultiplexed: 17. the following bits are unmultiplexed in desk top and are also 1: 0, 1, 2, 24 and 26. 2. if gpio[n] does not exist, then, the (n-32) bit in this register will always read as 0 and writes will have no effect. the followin g bits are always 0: 29, 30 and 31. 3. after a full reset rsmrst# all multiplexed signals in the resume and core wells are configured as their default function. after only a pltrst#, the gpios in the core well are config ured as their de fault function. 4. when configured to gpio mode, the muxing logic will present the inactive state to native logic that uses the pin as an input. 5. bit 26 is ignored, functionality is conf igured by bits 9:8 of flmap0 register. this register corresponds to gpio[63:32]. bit 0 corresponds to gpio32 and bit 28 corresponds to gpio60. 31:29 consumer only always 0. no corresponding gpio. 28:0 consumer only gpio_use_sel2[63:32] ? r/w. each bit in this register enables the corresponding gpio (if it exis ts) to be used as a gpio, rather than for the native function. 0 = signal used as native function. 1 = signal used as a gpio. notes: 1. the following bit is always 1 because it is always unmultiplexed: 17. the following bits are unmultiplexed in desk top and are also 1: 0, 1, 2, 24 and 26. 2. if gpio[n] does not exist, then, the (n-32) bit in this register will always read as 0 and writes will have no effect. the followin g bits are always 0: 29, 30 and 31. 3. after a full reset rsmrst# all multiplexed signals in the resume and core wells are configured as their default function. after only a pltrst#, the gpios in the core well are config ured as their de fault function. 4. when configured to gpio mode, the muxing logic will present the inactive state to native logic that uses the pin as an input. 5. bit 26 is ignored, functionality is conf igured by bits 9:8 of flmap0 register. this register corresponds to gpio[63:32]. bit 0 corresponds to gpio32 and bit 28 corresponds to gpio60. http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 498 datasheet 13.10.10 gp_io_sel2?gpio input/ output select 2 register offset address: gpiobase +34h attribute: r/w default value: 1b55fff0h (consumer only) size: 32-bit tbdh (corporate only) lockable: yes power well: core for 0:7, 16:23, resume for 8:15, 24:31 13.10.11 gp_lvl2?gpio level for input or output 2 register offset address: gpiobase +38h attribute: r/w default value: 1ffefff3h (consumer only) size: 32-bit tbdh (corporate only) lockable: yes power well: core for 0:7, 16:23, resume for 8:15, 24:31 bit description 31:0 corporate only gp_io_sel2[63:32] ? r/w. 0 = gpio signal is programmed as an output. 1 = corresponding gpio signal (if enab led in the gpio_use_sel2 register) is programmed as an input. this register correspon ds to gpio[63:32]. bit 0 corresponds to gpio32. 31:29 consumer only always 0. no corresponding gpio. 28:0 consumer only gp_io_sel2[63:32] ? r/w. 0 = gpio signal is programmed as an output. 1 = corresponding gpio signal (if enab led in the gpio_use_sel2 register) is programmed as an input. this register correspon ds to gpio[63:32]. bit 0 corresponds to gpio32. bit description 31:0 corporate only gp_lvl[63:32] ? r/w. if gpio[n] is programmed to be an output (via the corresponding bit in the gp_io_sel register), then the corresponding gp_lvl[n ] bit can be updated by software to drive a high or low value on the output pin. 1 = high, 0 = low. if gpio[n] is programmed as an input, th en the corresponding gp_lvl bit reflects the state of the input signal (1 = high, 0 = low.) and writes wi ll have no effect. when configured in native mode (gpio_use_sel[n] is 0), writes to these bits have no effect. the value reported in this re gister is undefined when programmed as native mode. this register correspon ds to gpio[63:32]. bit 0 corresponds to gpio32. 31:29 consumer only reserved. read-only 0 28:0 consumer only gp_lvl[63:32] ? r/w. if gpio[n] is programmed to be an output (via the corresponding bit in the gp_io_sel register), then the corresponding gp_lvl[n ] bit can be updated by software to drive a high or low value on the output pin. 1 = high, 0 = low. if gpio[n] is programmed as an input, th en the corresponding gp_lvl bit reflects the state of the input signal (1 = high, 0 = low.) and writes wi ll have no effect. when configured in native mode (gpio_use_sel[n] is 0), writes to these bits have no effect. the value reported in this re gister is undefined when programmed as native mode. this register correspon ds to gpio[63:32]. bit 0 corresponds to gpio32. http://www..net/ datasheet pdf - http://www..net/ datasheet 499 lpc interface bridge registers (d31:f0) 13.10.12 gpio_use_sel3?gpio use se lect 3 register (corporate only) offset address: gpiobase +40h attribute: r/w default value: tbdh size: 32-bit lockable: yes power well: core for 0:7, 16:23, resume for 8:15, 24:31 13.10.13 gp_io_sel3?gpio input/ output select 3 register (corporate only) offset address: gpiobase +44h attribute: r/w default value: 00000x00h size: 32-bit lockable: yes power well: core for 0:7, 16:23, resume for 8:15, 24:31 bit description 31:9 always 0. no corresponding gpio. 8 gpio_use_sel3[72] ? r/w. each bit in this register enables the corresponding gpio (if it exists) to be used as a gpio, rather than for the native function. 0 = signal used as native function. 1 = signal used as a gpio. notes: 1. if gpio[n] does not exist, then, the (n-32) bit in this register will always read as 0 and writes will have no effect. 2. after a full reset rsmrst# all multiplexe d signals in the resume and core wells are configured as their defa ult function. after only a pltrst#, the gpios in the core well are configured as their default function. 3. when configured to gpio mode, the muxi ng logic will present the inactive state to native logic that uses the pin as an input. this register corresponds to gpio[95:64]. bit 0 corresponds to gpio64 and bit 32 corresponds to gpio95. 7:0 always 0. no corresponding gpio. bit description 31:9 always 0. no corresponding gpio. 8 gp_io_sel3[72] ? r/w. 0 = gpio signal is programmed as an output. 1 = corresponding gpio signal (if enab led in the gpio_use_sel3 register) is programmed as an input. this register corresponds to gpio[9 5:64]. bit 0 corresponds to gpio64. 7:0 always 0. no corresponding gpio. http://www..net/ datasheet pdf - http://www..net/ lpc interface bridge registers (d31:f0) 500 datasheet 13.10.14 gp_lvl3?gpio level for input or output 3 register (corporate only) offset address: gpiobase +48h attribute: r/w default value: 1ffefff3h size: 32-bit lockable: yes power well: core for 0:7, 16:23, resume for 8:15, 24:31 13.10.15 gp_rst_sel ? gpio reset select offset address: gpiobase +60h attribute: r/w default value: 00000000h size: 32-bit lockable: yes power well: core for 0:7, 16:23, resume for 8:15, 24:31 bit description 31:9 reserved. read-only 0 8 gp_lvl[72] ? r/w. if gpio[n] is programmed to be an output (via the corresponding bit in the gp_io_sel register), then the corresponding gp_lvl[n] bit can be updated by software to drive a high or low value on the output pin. 1 = high, 0 = low. if gpio[n] is programmed as an input, then the corresponding gp_l vl bit reflects the state of the input signal (1 = high, 0 = low.) and writes will have no effect. when configured in native mode (gpio_use_se l[n] is 0), writes to these bits have no effect. the value reported in this register is undefined when programmed as native mode. this register corresponds to gpio[9 5:64]. bit 0 corresponds to gpio64. 7:0 reserved. read-only 0 bit description 31:11 reserved 10 gpio_rst_sel [31:00] - r/w. corresponding registers wi ll be reset by intern al suspend well reset. corresponding register s will be reset by rsmrst# pin only. note: in ich10, only th e reset for gpio10 is selectable between rsmrst# pin and internal resume well reset. all the gp_rst_sel registers are only reset-able by rsmrst# pin. 9:0 reserved http://www..net/ datasheet pdf - http://www..net/ datasheet 501 sata controller registers (d31:f2) 14 sata controller registers (d31:f2) 14.1 pci configuration registers (sata?d31:f2) note: address locations that are not shown should be treated as reserved. all of the sata registers are in the core well. none of the registers can be locked. table 14-1. sata controller pci register address map (sata?d31:f2) (sheet 1 of 2) offset mnemonic register name default type 00h?01h vid vendor identification 8086h ro 02h?03h did device identification see register description ro 04h?05h pcicmd pci command 0000h r/w, ro 06h?07h pcists pci status 02b0h r/wc, ro 08h rid revision identification see register description ro 09h pi programming interface see register description see register description 0ah scc sub class code see register description see register description 0bh bcc base class code 01h ro 0dh pmlt primary master latency timer 00h ro 0eh htype header type 00h ro 10h?13h pcmd_bar primary command block base address 00000001h r/w, ro 14h?17h pcnl_bar primary control block base address 00000001h r/w, ro 18h?1bh scmd_bar secondary command block base address 00000001h r/w, ro 1ch?1fh scnl_bar secondary control block base address 00000001h r/w, ro 20h?23h bar legacy bus master base address 00000001h r/w, ro 24h?27h abar / sidpba ahci base address / sata index data pair base address see register description see register description 2ch?2dh svid subsystem vendor identification 0000h r/wo 2eh?2fh sid subsystem identification 0000h r/wo 34h cap capabilities pointer 80h ro 3ch int_ln interrupt line 00h r/w 3dh int_pn interrupt pin see register description ro 40h-41h ide_tim primary ide timing register 0000h r/w http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 502 datasheet note: the ich10 sata controller is not arbitrated as a pci device, therefore it does not need a master latency timer. 42h-43h ide_tim secondary ide timing register 0000h r/w 70h?71h pid pci power management capability id see register description ro 72h?73h pc pci power management capabilities see register description ro 74h?75h pmcs pci power management control and status see register description r/w, ro, r/wc 80h?81h msici message signaled in terrupt capability id 7005h ro 82h?83h msimc message signaled interrupt message control 0000h ro, r/w 84h?87h msima message signaled interrupt message address 00000000h ro, r/w 88h?89h msimd message signaled interrupt message data 0000h r/w 90h map address map 0000h r/w 92h?93h pcs port control and status 0000h r/w, ro 94h-97h scgc sata clock gating control 00000000h r/w 9ch-9fh sclkgc sata clock general configuration 00000000h r/w, r/wo a8h-abh scap0 sata capability register 0 0010b012h ro, r/wo ach-afh scap1 sata capability register 1 00000048h ro b0h-b1h flrcid flr capability id 0009h ro b2h-b3h flrclv flr capability length and version see register description r/wo, ro b4h-b5h flrctrl flr control 0000h ro, r/w c0h atc apm trapping control 00h r/w c4h ats atm trapping status 00h r/wc d0h?d3h sp scratch pad 00000000h r/w e0h?e3h bfcs bist fis control/status 00000000h r/w, r/wc e4h?e7h bftd1 bist fis transmit data, dw1 00000000h r/w e8h?ebh bftd2 bist fis transmit data, dw2 00000000h r/w table 14-1. sata controller pci register address map (sata?d31:f2) (sheet 2 of 2) offset mnemonic register name default type http://www..net/ datasheet pdf - http://www..net/ datasheet 503 sata controller registers (d31:f2) 14.1.1 vid?vendor identificati on register (sata?d31:f2) offset address: 00h ? 01h attribute: ro default value: 8086h size: 16 bit lockable: no power well: core 14.1.2 did?device identificati on register (sata?d31:f2) offset address: 02h ? 03h attribute: ro default value: see bit description size: 16 bit lockable: no power well: core 14.1.3 pcicmd?pci command register (sata?d31:f2) address offset: 04h ? 05h attribute: ro, r/w default value: 0000h size: 16 bits bit description 15:0 vendor id ? ro. this is a 16-bit value assigned to intel. intel vid = 8086h bit description 15:0 device id ? ro. this is a 16-bit value assigned to the intel ? ich10 sata controller. note: the value of this field will change dependent upon the value of the map register. see section 14.1.30 bit description 15:11 reserved 10 interrupt disable ? r/w. this disables pin-based intx# interrupts. this bit has no effect on msi operation. 0 = internal intx# messages are generated if there is an interrupt and msi is not enabled. 1 = internal intx# messages will not be generated. 9 fast back to back enable (fbe) ? ro. reserved as 0. 8 serr# enable (serr_en) ? ro. reserved as 0. 7 wait cycle control (wcc) ? ro. reserved as 0. 6 parity error response (per) ? r/w. 0 = disabled. sata controller will not gene rate perr# when a data parity error is detected. 1 = enabled. sata controller will generate perr# when a data pari ty error is detected. 5 vga palette snoop (vps) ? ro. reserved as 0. 4 postable memory write enable (pmwe) ? ro. reserved as 0. 3 special cycle en able (sce) ? ro. reserved as 0. 2 bus master enable (bme) ? r/w. this bit controls the ich10?s ability to act as a pci master for ide bus master transfers. this bit does not impact the generation of completions for split transaction commands. 1 memory space enable (mse) ? r/w / ro. controls access to the sata controller?s target memory space (for ahci). this bi t is ro ?0? when not in ahci/raid modes. http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 504 datasheet 14.1.4 pcists ? pci status register (sata?d31:f2) address offset: 06h ? 07h attribute: r/wc, ro default value: 02b0h size: 16 bits note: for the writable bits, software must write a 1 to clear bits that are set. writing a 0 to the bit has no effect. 0 i/o space enable (iose) ? r/w. this bit controls access to the i/o space registers. 0 = disables access to the legacy or native ide ports (both primar y and secondary) as well as the bus mast er i/o registers. 1 = enable. note that the base address regist er for the bus master registers should be programmed before this bit is set. bit description bit description 15 detected parity error (dpe) ? r/wc. 0 = no parity error detected by sata controller. 1 = sata controller detects a parity error on its interface. 14 signaled system error (sse) ? ro. reserved as 0. 13 received master abort (rma) ? r/wc. 0 = master abort not generated. 1 = sata controller, as a master , generated a master abort. 12 reserved as 0 ? ro. 11 signaled target abort (sta) ? ro. reserved as 0. 10:9 devsel# timing status (dev_sts) ? ro. 01 = hardwired; controls the devi ce select time for the sata controller?s pci interface. 8 data parity error detected (dped) ? r/wc. for ich10, this bit can only be set on read completions received from the bus when there is a parity error. 1 = sata controller, as a master, either detect s a parity error or sees the parity error line asserted, and the parity error response bit (bit 6 of the command register) is set. 7 fast back to back capable (fb2bc) ? ro. reserved as 1. 6 user definable features (udf) ? ro. reserved as 0. 5 66mhz capable (66mhz_cap) ? ro. reserved as 1. 4 capabilities list (cap_list) ? ro. this bit indicates the presence of a capabilities list. the minimum requirement for the capabili ties list must be pci power management for the sata controller. 3 interrupt status (ints) ? ro. reflects the state of intx# messages, irq14 or irq15. 0 = interrupt is cleared (ind ependent of the state of in terrupt disabl e bit in the command register [offset 04h]). 1 = interrupt is to be asserted 2:0 reserved http://www..net/ datasheet pdf - http://www..net/ datasheet 505 sata controller registers (d31:f2) 14.1.5 rid?revision identificati on register (sata?d31:f2) offset address: 08h attribute: ro 14.1.6 pi?programmin g interface register (sata?d31:f2) 14.1.6.1 when sub class code register (d31:f2:offset 0ah) = 01h address offset: 09h attribute: r/w, ro default value: see bit description size: 8 bits bit description 7:0 revision id ? ro. refer to the intel ? i/o controller hub (ich10) specification update for the value of the revision id register bit description 7 this read-only bit is a 1 to indicate th at the ich10 supports bus master operation 6:4 reserved. will always return 0. 3 secondary mode native capable (snc) ? ro. 0 = secondary controller only supports legacy mode. 1 = secondary controller supports both legacy and native modes. when map.mv (d31:f2:offset 90:bits 1:0) is any value other than 00b, this bit reports as a 0. when map.mv is 00b , this bit reports as a 1. 2 secondary mode nati ve enable (sne) ? r/w. determines the mode th at the secondary channel is operating in. 0 = secondary controller operatin g in legacy (compatibility) mode 1 = secondary controller operating in native pci mode. when map.mv (d31:f2:offset 90:bits 1:0) is any value other than 00b, this bit is read- only (ro). when map.mv is 00b, this bit is read/write (r/w). if this bit is set by software, then the pne bit (bit 0 of this register ) must also be set by software. while in theory these bits can be programmed separately, such a configuration is not supported by hardware. 1 primary mode native capable (pnc) ? ro. 0 = primary controller only supports legacy mode. 1 = primary controller supports both legacy and native modes. when map.mv (d31:f2:offset 90:bits 1:0) is any value other than 00b, this bit reports as a 0. when map.mv is 00b , this bit reports as a 1 0 primary mode native enable (pne) ? r/w. determines the mode that the primary channel is operating in. 0 = primary controller operating in legacy (compatibility) mode. 1 = primary controller operating in native pci mode. if this bit is set by software, then the sne bit (bit 2 of this register) must also be set by software simultaneously. http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 506 datasheet 14.1.6.2 when sub class code regi ster (d31:f2:offset 0ah) = 04h address offset: 09h attribute: ro default value: 00h size: 8 bits 14.1.6.3 when sub class code regi ster (d31:f2:offset 0ah) = 06h address offset: 09h attribute: ro default value: 01h size: 8 bits 14.1.7 scc?sub class code register (sata?d31:f2) address offset: 0ah attribute: ro default value: see bit description size: 8 bits 14.1.8 bcc?base class code register (sata?d31:f2) address offset: 0bh attribute: ro default value: 01h size: 8 bits bit description 7:0 interface (if) ? ro. when configured as raid, this register becomes read only 0. bit description 7:0 interface (if) ? ro. indicates the sata controll er supports ahci, rev 1.2. bit description 7:0 sub class code (scc) this field specifies the sub-class code of the controller, per the table below: intel ? ich10 only: intel ? matrix storage technology enabled ich10 components only: scc register attribute scc register value ro 01h (ide controller) map.sms (d31:f2:offset 90h:bit 7:6) scc default register value 00b 01h (ide controller) 01b 06h (ahci controller) 10b 04h (raid controller) bit description 7:0 base class code (bcc) ? ro. 01h = mass storage device http://www..net/ datasheet pdf - http://www..net/ datasheet 507 sata controller registers (d31:f2) 14.1.9 pmlt?primary master latency timer register (sata?d31:f2) address offset: 0dh attribute: ro default value: 00h size: 8 bits 14.1.10 htype?header type (sata?d31:f2) address offset: 0eh attribute: ro default value: 00h size: 8 bits 14.1.11 pcmd_bar?primary co mmand block base address register (sata?d31:f2) address offset: 10h ? 13h attribute: r/w, ro default value: 00000001h size: 32 bits . note: this 8-byte i/o space is used in native mo de for the primary controller?s command block. bit description 7:0 master latency timer count (mltc) ? ro. 00h = hardwired. the sata controller is im plemented internally, and is not arbitrated as a pci device, so it does no t need a master latency timer. bit description 7 multi-function device (mfd) ? ro. indicates this sata controller is no t part of a multifunction device. 6:0 header layout (hl) ? ro. indicates that the sata controller uses a target device layout. bit description 31:16 reserved 15:3 base address ? r/w. this field provides the ba se address of the i/o space (8 consecutive i/o locations). 2:1 reserved 0 resource type indicator (rte) ? ro. hardwired to 1 to indicate a request for i/o space. http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 508 datasheet 14.1.12 pcnl_bar?primary contro l block base address register (sata?d31:f2) address offset: 14h ? 17h attribute: r/w, ro default value: 00000001h size: 32 bits . note: this 4-byte i/o space is used in native mo de for the primary cont roller?s command block. 14.1.13 scmd_bar?secondary co mmand block base address register (ide d31:f1) address offset: 18h ? 1bh attribute: r/w, ro default value: 00000001h size: 32 bits note: this 4-byte i/o space is used in native mode for the secondary controller?s command block. 14.1.14 scnl_bar?secondary co ntrol block base address register (ide d31:f1) address offset: 1ch ? 1fh attribute: r/w, ro default value: 00000001h size: 32 bits note: this 4-byte i/o space is used in native mode for the secondary controller?s command block. bit description 31:16 reserved 15:2 base address ? r/w. this field provides the base address of the i/o space (4 consecutive i/o locations). 1 reserved 0 resource type indicator (rte) ? ro. hardwired to 1 to indicate a request for i/o space. bit description 31:16 reserved 15:3 base address ? r/w. this field provides the ba se address of the i/o space (8 consecutive i/o locations). 2:1 reserved 0 resource type indicator (rte) ? ro. hardwired to 1 to indicate a request for i/o space. bit description 31:16 reserved 15:2 base address ? r/w. this field provides the ba se address of the i/o space (4 consecutive i/o locations). 1reserved 0 resource type indicator (rte) ? ro. hardwired to 1 to indicate a request for i/o space. http://www..net/ datasheet pdf - http://www..net/ datasheet 509 sata controller registers (d31:f2) 14.1.15 bar ? legacy bus mast er base address register (sata?d31:f2) address offset: 20h ? 23h attribute: r/w, ro default value: 00000001h size: 32 bits the bus master ide interface function uses base address register 5 to request a 16- byte io space to provide a software interface to the bus master functions. only 12 bytes are actually used (6 bytes for primary, 6 bytes for secondary). only bits [15:4] are used to decode the address. 14.1.16 abar/sidpba1 ? ahci base address register/serial ata index data pair base address (sata?d31:f2) when the programming interface is not ide (i.e. scc is not 01h), this register is named abar. when the programming interface is ide, this register becomes sidpba. note that hardware does not clear those ba bits when switching from ide component to non-ide component or vice versa. bios is responsible for clearing those bits to 0 since the number of writable bits changes after component switching (as indicated by a change in scc). in th e case, this register will then have to be re-programmed to a proper value. 14.1.16.1 when scc is not 01h when the programming interface is not ide, the register represents a memory bar allocating space for the ahci memory registers defined in section 14.4 . . address offset: 24-27h attribute: r/w, ro default value: 00000000h size: 32 bits note: 1. the abar register must be set to a value of 0001_0000h or greater. bit description 31:16 reserved 15:5 base address ? r/w. this field provides the base address of the i/o space (16 consecutive i/o locations). 4 base ? r/w / ro. when scc is 01h, this bit will be r/w resulting in requesting 16b of i/o space. when scc is not 01h, this bit will be read only 0, resulting in requesting 32b of i/o space. 3:1 reserved 0 resource type indicator (rte) ? ro. hardwired to 1 to indicate a request for i/o space. bit description 31:11 base address (ba) ? r/w. base address of register memory space (aligned to 1 kb) 10:4 reserved 3 prefetchable (pf) ? ro. indicates that this range is not pre-fetchable 2:1 type (tp) ? ro. indicates that this range can be mapped anywhere in 32-bit address space. 0 resource type indicator (rte) ? ro. hardwired to 0 to indicate a request for register memory space. http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 510 datasheet 14.1.16.2 when scc is 01h when the programming interface is ide, the register becomes an i/o bar allocating 16 bytes of i/o space for the i/o-mapped registers defined in section 14.2 . note that although 16 bytes of locations are allocated, only 8 bytes are used to as sindx and sdata registers; with the remaining 8 bytes preserved for future enhancement. address offset: 24h ? 27h attribute: r/wo default value: 00000001h size: 32 bits 14.1.17 svid?subsystem vendor identification register (sata?d31:f2) address offset: 2ch ? 2dh attribute: r/wo default value: 0000h size: 16 bits lockable: no power well: core function level reset: no 14.1.18 sid?subsystem identifica tion register (sata?d31:f2) address offset: 2eh ? 2fh attribute: r/wo default value: 0000h size: 16 bits lockable: no power well: core function level reset: no 14.1.19 cap?capabilities poin ter register (sata?d31:f2) address offset: 34h attribute: ro default value: 80h size: 8 bits bit description 31:16 reserved 15:4 base address (ba) ? r/w. base address of the i/o space. 3:1 reserved 0 resource type indicator (rte) ? ro. indicates a request for i/o space. bit description 15:0 subsystem vendor id (svid) ? r/wo. value is written by bios. no hardware action taken on this value. bit description 15:0 subsystem id (sid) ? r/wo. value is written by bios. no hardware action taken on this value. bit description 7:0 capabilities pointer (cap_ptr) ? ro. indicates that the first capability pointer offset is 80h. this value changes to 70h if the sub class code (scc) (dev 31:f2:0ah) is configure as ide mode (value of 01). http://www..net/ datasheet pdf - http://www..net/ datasheet 511 sata controller registers (d31:f2) 14.1.20 int_ln?interrupt line register (sata?d31:f2) address offset: 3ch attribute: r/w default value: 00h size: 8 bits function level reset: no 14.1.21 int_pn?interrupt pi n register (sata?d31:f2) address offset: 3dh attribute: ro default value: see register description size: 8 bits 14.1.22 ide_tim ? ide timing register (sata?d31:f2) address offset: primary: 40h ? 41h attribute: r/w secondary: 42h ? 43h default value: 0000h size: 16 bits 14.1.23 pid?pci power management capability identification register (sata?d31:f2) address offset: 70h ? 71h attribute: ro default value: xx01h size: 16 bits bit description 7:0 interrupt line ? r/w. this field is used to communicate to software the interrupt line that the interrupt pin is connected to. interrupt line register is not reset by flr. bit description 7:0 interrupt pin ? ro. this reflects the value of d31ip.sip (chipset config registers:offset 3100h:bits 11:8). bit description 15 ide decode enable (ide) ? r/w. individually enable/disabl e the primary or secondary decode. 0 = disable. 1 = enables the intel ? ich10 to decode the associated comma nd blocks (1f0?1f7h for primary, 170?177h for secondary) and control block (3f6h for primary and 376h for secondary). this bit effects the ide decode ranges for both legacy and native-mode decoding. note: this bit affects sata operation in both combined and non-combined ata modes. see section 5.16 for more on ata modes of operation. 14:0 reserved bits description 15:8 next capability (next) ? ro. b0h ? if scc = 01h (ide mode) indicating next item is flr capability pointer. a8h ? for all other values of scc to po int to the next capability structure. 7:0 capability id (cid) ? ro. indicates that this pointer is a pci power management. http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 512 datasheet 14.1.24 pc?pci power manageme nt capabilities register (sata?d31:f2) address offset: 72h ? 73h attribute: ro default value: x003h size: 16 bits f 14.1.25 pmcs?pci power mana gement control and status register (sata?d31:f2) address offset: 74h ? 75h attribute: r/w, r/wc default value: xx08h size: 16 bits function level reset: no (bits 8 and 15) bits description 15:11 pme support (pme_sup) ? ro. 00000 = if scc = 01h, indicates no pme support in ide mode. 01000 = if scc is not 01h, in a non-ide mode, indicates pme# can be generated from the d3 hot state in the sata host controller. 10 d2 support (d2_sup) ? ro. hardwired to 0. the d2 state is not supported 9 d1 support (d1_sup) ? ro. hardwired to 0. the d1 state is not supported 8:6 auxiliary current (aux_cur) ? ro. pme# from d3 cold state is not supported, therefore this field is 000b. 5 device specific initialization (dsi) ? ro. hardwired to 0 to indicate that no device- specific initialization is required. 4 reserved 3 pme clock (pme_clk) ? ro. hardwired to 0 to in dicate that pci clock is not required to generate pme#. 2:0 version (ver) ? ro. hardwired to 011 to indicates support for revision 1.2 of the pci power management specification. bits description 15 pme status (pmes) ? r/wc. bit is set when a pme ev ent is to be requested, and if this bit and pmee is set, a pme# will be generated from the sata controller note: whenever scc = 01h, hardware will automatically change the attribute of this bit to ro ?0?. software is advised to clear pm ee and pmes together prior to changing scc thru map.sms. this bit is not reset by function level reset. 14:9 reserved 8 pme enable (pmee) ? r/w. when set, the sata co ntroller generates pme# form d3 hot on a wake event. note: whenever sccscc = 01h, hardware will automatically change the attribute of this bit to ro ?0?. software is advised to cl ear pmee and pmes together prior to changing scc thru map.sms. this bit is not reset by function level reset. 7:4 reserved http://www..net/ datasheet pdf - http://www..net/ datasheet 513 sata controller registers (d31:f2) 14.1.26 msici?message signal ed interrupt capability identification (sata?d31:f2) address offset: 80h ? 81h attribute: ro default value: 7005h size: 16 bits note: there is no support for msi when the software is operating in legacy (ide) mode when ahci is not enabled. prior to switch ing from ahci to ide mode, software must make sure that msi is disabled. 3 no soft reset (nsfrst) ? ro. these bits are used to indicate whether devices transitioning from d3 hot state to d0 state will perform an internal reset. 0 = device transitioning from d3 hot state to d0 state perfo rm an internal reset. 1 = device transitioning from d3 hot state to d0 state do not perform an internal reset. configuration content is preserved. upon transition from the d3 hot state to d0 state initialized state, no addition al operating system interventi on is required to preserve configuration context beyond writing to the powerstate bits. regardless of this bit, the controller transition from d3 hot state to d0 state by a system or bus segment reset will return to the state d0 uninitialized with only pme context preserved if pme is supported and enabled. 2reserved 1:0 power state (ps) ? r/w. these bits are used both to determine the current power state of the sata controller and to set a new power state. 00 = d0 state 11 = d3 hot state when in the d3 hot state, the controller?s configurat ion space is available, but the i/o and memory spaces are not. addi tionally, interrupts are blocked. bits description bits description 15:8 next pointer (next) ? ro. indicates the next item in the list is the pci power management pointer. 7:0 capability id (cid) ? ro. capabilities id indicates msi. http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 514 datasheet 14.1.27 msimc?message signaled interrupt message control (sata?d31:f2) address offset: 82h ? 83h attribute: r/w, ro default value: 0000h size: 16 bits note: there is no support for msi when the software is operating in legacy (ide) mode when ahci is not enabled. prior to switching from ahci to ide mode, software must make sure that msi is disabled. bits description 15:8 reserved 7 64 bit address capable (c64) ? ro. capable of generating a 32-bit message only. 6:4 multiple message enable (mme) ? r/w. = 000 (and msie is set), a single msi messag e will be generated fo r all sata ports, and bits [15:0] of the message vector will be driven from md[15:0]. values ?011b? to ?111b? are reserved. if this field is set to one of these reserved values, the results are undefined. note: note: the ccc interrupt is generated on unimplemented port (ahci pi register bit equal to 0). if ccc interrupt is disa bled, no msi shall be generated for the port dedicated to the ccc interrupt. wh en ccc interrupt occurs, md[2:0] is dependant on ccc_ctl.int (in addition to mme). for 6 port components: mme value driven on msi memory write bits[15:3] bit[2] bit[1] bit[0] 000, 001, 010 md[15:3] md[2] md[1] md[0] 100 md[15:3] port 0: 0 port 1: 0 port 2: 0 port 3: 0 port 4: 1 port 5: 1 port 0: 0 port 1: 0 port 2: 1 port 3: 1 port 4: 0 port 5: 0 port 0: 0 port 1: 1 port 2: 0 port 3: 1 port 4: 0 port 5: 1 for 4 port components: mme value driven on msi memory write bits[15:3] bit[2] bit[1] bit[0] 000, 001, 010 md[15:3] md[2] md[1] md[0] 100 md[15:3] port 0: 0 port 1: 0 port 4: 1 port 5: 1 port 0: 0 port 1: 0 port 2: 0 port 3: 0 port 0: 0 port 1: 1 port 2: 0 port 3: 1 http://www..net/ datasheet pdf - http://www..net/ datasheet 515 sata controller registers (d31:f2) 14.1.28 msima? message signaled interrupt message address (sata?d31:f2) address offset: 84h ? 87h attribute: r/w default value: 00000000h size: 32 bits note: there is no support for msi when the software is operating in legacy (ide) mode when ahci is not enabled. prior to switch ing from ahci to ide mode, software must make sure that msi is disabled. 14.1.29 msimd?message signaled interrupt message data (sata?d31:f2) address offset: 88h-89h attribute: r/w default value: 0000h size: 16 bits note: there is no support for msi when the software is operating in legacy (ide) mode when ahci is not enabled. prior to switch ing from ahci to ide mode, software must make sure that msi is disabled. 3:1 multiple message capable (mmc) ? ro. indicates the numbe r of interrupt messages supported by the ich10 sata controller. 000 =1 msi capable (when scc bit is set to 01h. msi is not supported in ide mode) 100 = 8 msi capable 0 msi enable (msie) ? r/w /ro. if set, msi is enabled and traditional interrupt pins are not used to generate interrupts. this bit is rw when sc.scc is not 01h and is read- only 0 when scc is 01h. note that cmd.id bit has no effect on msi. note: software must clear this bit to ?0? to disable msi first before changing the number of messages allocated in the mmc field. software must also make sure this bit is cleared to ?0? when operat ing in legacy mode (when ghc.ae = 0). bits description bits description 31:2 address (addr) ? r/w. lower 32 bits of the sy stem specified message address, always dword aligned. 1:0 reserved bits description 15:0 data (data) ? r/w. this 16-bit field is programmed by system software if msi is enabled. its content is driven onto the lowe r word of the data bus of the msi memory write transaction. note that when the mme fiel d is set to ?001? or ?010?, bit [0] and bits [1:0] respectively of the msi memory write transaction will be driven based on the source of the interrupt rather than from md [2:0]. see the description of the mme field. http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 516 datasheet 14.1.30 map?address map re gister (sata?d31:f2) address offset: 90h attribute: r/w, r/wo default value: 0000h size: 16 bits function level reset: no (bits 7:5 and 13:8 only) 14.1.31 pcs?port control and status register (sata?d31:f2) address offset: 92h ? 93h attribute: r/w, ro default value: 0000h size: 16 bits function level reset: no by default, the sata ports are set to the di sabled state (bits [5:0] = ?0?). when enabled by software, the ports can transition between the on, partial, and slumber states and can detect devices. when disabled, the port is in the ?off? state and cannot detect any devices. if an ahci-aware or raid enabled operating system is being booted, then system bios shall insure that all supported sata ports are enabled prior to passing control to the os. once the ahci aware os is booted it becomes the enabling/disabling policy owner for the individual sata ports. this is acco mplished by manipulating a port?s pxsctl and bits description 15:14 reserved 13:8 reserved 7:6 sata mode select (sms) ? r/w. sw programs these bits to control the mode in which the sata controller should operate: 00b = ide mode 01b = ahci mode 10b = raid mode 11b = reserved notes: 1. the sata function device id will chan ge based on the value of this register. 2. when switching from ahci or raid mode to ide mode, a 2 port sata controller (device 31, function 5) will be enabled. 3. ahci mode may only be selected when mv = 00 4. raid mode may only be selected when mv = 00 5. programming these bits with values that are invalid (e.g. selecting raid when in combined mode) will result in indeterministic behavior by the hw 6. sw shall not manipulate sms during runt ime operation; i.e. the os will not do this. the bios may choose to switch fro m one mode to another during post. these bits are not reset by function level reset. 5 sata port-to-controller configuration (sc) ? r/w. this bit changes the number of sata ports available within each sata controller. 0 = up to 4 sata ports are available for cont roller 1 (device 31 func tion 2) with ports [3:0] and up to 2 sata ports are available for controller 2 (device 31 function 5) with ports [5:4]. 1 = up to 6 sata ports are available for cont roller 1 (device 31 func tion 2) with ports [5:0] and no sata ports are available fo r controller 2 (device 31 function 5). note: this bit should be set to 1 only in ahci mode. this bit is no t reset by function level reset. 4:2 reserved. 1:0 map value (mv) ? ro. reserved http://www..net/ datasheet pdf - http://www..net/ datasheet 517 sata controller registers (d31:f2) pxcmd fields. because an ahci or raid awar e os will typically not have knowledge of the pxe bits and because the pxe bits act as master on/off switches for the ports, pre- boot software must insure that these bits are set to ?1? prior to booting the os, regardless as to whether or not a device is currently on the port. bits description 15 oob retry mode (orm) ? rw. 0 = the sata controller will not retry after an oob failure 1 = the sata controller will continue to retry after an oob fail ure until successful (infinite retry) 14 reserved. 13 port 5 present (p5p) ? ro. the status of this bit ma y change at any time. this bit is cleared when the port is disabled via p5 e. this bit is not cleared upon surprise removal of a device. 0 = no device detected. 1 = the presence of a device on port 5 has been detected. 12 port 4 present (p4p) ? ro. the status of this bit ma y change at any time. this bit is cleared when the port is disabled via p4 e. this bit is not cleared upon surprise removal of a device. 0 = no device detected. 1 = the presence of a device on port 4 has been detected. 11 port 3 present (p3p) ? ro. the status of this bit ma y change at any time. this bit is cleared when the port is disabled via p3 e. this bit is not cleared upon surprise removal of a device. 0 = no device detected. 1 = the presence of a device on port 3 has been detected. 10 port 2 present (p2p) ? ro. the status of this bit ma y change at any time. this bit is cleared when the port is disabled via p2 e. this bit is not cleared upon surprise removal of a device. 0 = no device detected. 1 = the presence of a device on port 2 has been detected. 9 port 1 present (p1p) ? ro. the status of this bit ma y change at any time. this bit is cleared when the port is disabled via p1 e. this bit is not cleared upon surprise removal of a device. 0 = no device detected. 1 = the presence of a device on port 1 has been detected. 8 port 0 present (p0p) ? ro. the status of this bit ma y change at any time. this bit is cleared when the port is disabled via p0 e. this bit is not cleared upon surprise removal of a device. 0 = no device detected. 1 = the presence of a device on port 0 has been detected. 7:6 reserved 5 port 5 enabled (p5e) ? r/w. 0 = disabled. the port is in the ?off? state and cannot detect any devices. 1 = enabled. the port can transition betwee n the on, partial, and slumber states and can detect devices. note: this bit takes precedence over p5cmd.sud (offset abar+298h:bit 1) if map.sc is ?0?, if scc is ?01h? this bit wi ll be read only ?0? or if map.spd[5] is ?1?. http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 518 datasheet 4 port 4 enabled (p4e) ? r/w. 0 = disabled. the port is in the ?off? state and cannot detect any devices. 1 = enabled. the port can transition betwee n the on, partial, an d slumber states and can detect devices. note: this bit takes precedence over p4cmd.sud (offset abar+298h:bit 1) if map.sc is ?0?, if scc is ?01h? this bit wi ll be read only ?0? or if map.spd[4] is ?1?. 3 port 3 enabled (p3e) ? r/w. 0 = disabled. the port is in the ?off? state and cannot detect any devices. 1 = enabled. the port can transition betwee n the on, partial, an d slumber states and can detect devices. note: this bit takes precedence over p3cm d.sud (offset abar+298h:bit 1). when map.spd[3] is ?1? this is reserved and is read-only 0. 2 port 2 enabled (p2e) ? r/w. 0 = disabled. the port is in the ?off? state and cannot detect any devices. 1 = enabled. the port can transition betwee n the on, partial, an d slumber states and can detect devices. note: this bit takes precedence over p2cm d.sud (offset abar+218h:bit 1). when map.spd[2] is ?1? this is reserved and is read-only 0. 1 port 1 enabled (p1e) ? r/w. 0 = disabled. the port is in the ?off? state and cannot detect any devices. 1 = enabled. the port can transition betwee n the on, partial, an d slumber states and can detect devices. note: this bit takes precedence over p1cm d.sud (offset abar+198h:bit 1). when map.spd[1] is ?1? this is reserved and is read-only 0. 0 port 0 enabled (p0e) ? r/w. 0 = disabled. the port is in the ?off? state and cannot detect any devices. 1 = enabled. the port can transition betwee n the on, partial, an d slumber states and can detect devices. note: this bit takes precedence over p0cm d.sud (offset abar+118h:bit 1). when map.spd[0] is ?1? this is reserved and is read-only 0. bits description http://www..net/ datasheet pdf - http://www..net/ datasheet 519 sata controller registers (d31:f2) 14.1.32 sclkcg?sata clock gating control register address offset: 94h-97h attribute: r/w default value: 00000000h size: 32 bits . bit description 31:30 reserved. 29:24 port clock disable (pcd) ? 0 = all clocks to the associated port logic will operate normally. 1 = the backbone clock driven to the asso ciated port logic is gated and will not toggle. bit 29: port 5 bit 28: port 4 bit 27: port 3 bit 26: port 2 bit 25: port 1 bit 24: port 0 if a port is not available, software shall set the corresponding bit to 1. software can also set the corresponding bits to 1 on ports that are disabled. software cannot set the pcd [port x]=?1? if the corresponding pcs.pxe=?1? in either dev31func2 or dev31func5 (dual controller ide mode). 23:9 reserved. 8:0 sclkcg field 1 ? r/w. bios must program these bits to 193h. http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 520 datasheet 14.1.33 sclkgc?sata clock gene ral configuration register address offset: 9ch-9fh attribute: r/w, r/wo default value: 00000000h size: 32 bits function level reset: no bit description 31:8 reserved 7 (ich10 base only) reserved 7 (ich10r, ich10do, and ich10d only) alternate id enable (aie) ? r/wo. 0 = when in raid mode the sata controller located at device 31: function 2 will report the following devi ce id 2822h for desktop and the microsoft windows vista* in-box version of the intel ? matrix storage manager will load on the platform. 1 = when in raid mode the sata controller located at device 31: function 2 will report the device id reported in the intel ? i/o controller hub 10 (ich10) family specification update to prevent the microsoft windows vista in-box version of the intel matrix storage ma nager from loading on the platform and will require the user to perform an ?f6? installation of the appropriate intel matrix storage manager. note: this field is applicable when the ah ci is configured for raid mode of operation. it has no impact for ahci and ide modes of operation. bios is recommended to program this bit prio r to programming the map.sms field to reflect raid. this field is reset by pltrst#. bios is required to reprogram the value of this bit af ter resuming from s3, s4 and s5. 6:2 sata traffic monitor? r/w. 00000b = disable. 00011b = enable. sata traffic monitor allows for aggressive c2 pop down by monitoring sata bus mastering activity. when enabled, bios must ensure bit 3 and bit 4 of cx_state_cnf (cx state configuration register) are ones. note: this field is reset by pltrst# and bios is required to reprogram the value after resuming from s3?s5. all other bit combinations are reserved. 1 sata2-port configuration indicator (sata2pind) ? ro. 0 = normal configuration. 1 = one ide controller is implemented supporting only two ports for a primary master and a secondary master. note: when set, bios must ensu re that bit 2 and bit 3 of the ahci pi registers are zeros. bios must also make sure that port 2 and port 3 are disabled (via pcs configuration register) and th e port clocks are gated (via sclkcg configuration register). 0 sata4-port all master configur ation indicator (sata4pmind) ? ro. 0 = normal configuration. 1 = two ide controllers are implemented, each supporting two ports for a primary master and a secondary master. note: when set, bios must ensu re that bit 2 and bit 3 of the ahci pi registers are zeros. bios must also make sure that port 2 and port 3 are disabled (via pcs configuration register) and th e port clocks are gated (via sclkcg configuration register). http://www..net/ datasheet pdf - http://www..net/ datasheet 521 sata controller registers (d31:f2) 14.1.33.1 satacr0?sata capabilit y register 0 (sata?d31:f2) address offset: a8h?abh attribute: ro, r/wo default value: 0010b012h size: 32 bits function level reset: no (bits 15:8 only) note: this register shall be read-only 0 when scc is 01h. 14.1.33.2 satacr1?sata capabilit y register 1 (sata?d31:f2) address offset: ach?afh attribute: ro default value: 00000048h size: 32 bits note: this register shall be read-only 0 when scc is 01h. bit description 31:24 reserved 23:20 major revision (majrev) ? ro: major revision number of the sata capability pointer implemented. 19:16 minor revision (minrev) ? ro: minor revision numbe r of the sata capability pointer implemented. 15:8 next capability pointer (next) ? r/wo: points to the next capability structure. these bits are not reset by function level reset. 7:0 capability id (cap) ? ro: this value of 12h has been assigned by the pci sig to designate the sata capability structure. bit description 31:16 reserved 15:4 bar offset (barofst) ? ro : indicates the offset into the bar where the index/data pair are located (in dword granularity). the index and data i/o regi sters are located at offset 10h within the i/o space defined by lbar. a value of 004h indicates offset 10h. 000h = 0h offset 001h = 4h offset 002h = 8h offset 003h = bh offset 004h = 10h offset ... fffh = 3fffh offset (max 16kb) 3:0 bar location (barloc) ? ro : indicates the absolute pci configuration register address of the bar containing the index/da ta pair (in dword granularity). the index and data i/o registers reside within the space defined by lbar in the sata controller. a value of 8h indicates offset 20h, which is lbar. 0000 ? 0011b = reserved 0100b = 10h => bar0 0101b = 14h => bar1 0110b = 18h => bar2 0111b = 1ch => bar3 1000b = 20h => lbar 1001b = 24h => bar5 1010 ? 1110b = reserved 1111b = index/data pair in pci configuration space. this isn?t supported in ich10. http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 522 datasheet 14.1.34 flrcid?flr capab ility id (sata?d31:f2) address offset: b0-b1h attribute: ro default value: 0009h size: 16 bits 14.1.35 flrclv?flr capability length and version (sata? d31:f2) address offset: b2-b3h attribute: ro, r/wo default value: xx06h size: 16 bits function level reset: no (bit 9:8 only when flrcssel = ?0?) when flrcssel = ?0?, this register is defined as follows: when flrcssel = ?1?, this register is defined as follows: bit description 15:8 next capability pointer ? ro. 00h indicates the final item in the capability list. 7:0 capability id ? ro. the value of this field depends on the flrcssel bit. 13h = if pflrcssel = 0 09h (vendor specific) = if pflrcssel = 1 bit description 15:10 reserved. 9 flr capability ? r/wo. 1 = support for function level reset. this bit is not reset by the function level reset. 8 txp capability ? r/wo. 1 = support for transactions pending (txp) bit. txp must be supported if flr is supported. 7:0 vendor-specific capability id ? ro. this field indicate s the # of bytes of this vendor specific capability as required by th e pci specification. it has the value of 06h for the flr capability. bit description 15:12 vendor-specific capability id ? ro. a value of 2h identifi es this capabi lity as the function level reset (flr). 11:8 capability version ? ro. this field indicates the version of the flr capability. 7:0 vendor-specific capability id ? ro. this field indicate s the # of bytes of this vendor specific capability as required by th e pci specification. it has the value of 06h for the flr capability. http://www..net/ datasheet pdf - http://www..net/ datasheet 523 sata controller registers (d31:f2) 14.1.36 flrc?flr cont rol (sata?d31:f2) address offset: b4-b5h attribute: ro, r/w default value: 0000h size: 16 bits 14.1.37 atc?apm trapping cont rol register (sata?d31:f2) address offset: c0h attribute: r/w default value: 00h size: 8 bits function level reset:no . bit description 15:9 reserved. 8 transactions pending (txp) ? ro. 0 = controller has received all non-posted requests. 1 = controller has issued non-posted requests which has not been completed. 7:1 reserved. 0 initiate flr ? r/w. used to initiate flr transition. a write of ?1? indicates flr transition. since hardware must no t respond to any cycles till flr completion the value read by software from this bit is ?0?. bit description 7:4 reserved 3 secondary slave trap (sst) ? r/w. enables trapping and smi# assertion on legacy i/o accesses to 170h-177h and 376h. the active device on the secondary interface must be device 1 for the tr ap and/or smi# to occur. 2 secondary master trap (spt) ? r/w. enables trapping and smi# assertion on legacy i/o accesses to 170h-177h and 37 6h. the active device on the secondary interface must be device 0 for the trap and/or smi# to occur. 1 primary slave trap (pst) ? r/w. enables trapping and smi# assertion on legacy i/ o accesses to 1f0h-1f7h and 3f6h. the active device on the primar y interface must be device 1 for the trap and/or smi# to occur. 0 primary master trap (pmt) ? r/w. enables trapping and smi# assertion on legacy i/o accesses to 1f0h-1f7h and 3f6h. the acti ve device on the pr imary interface must be device 0 for the trap and/or smi# to occur. http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 524 datasheet 14.1.38 ats?apm trapping stat us register (sata?d31:f2) address offset: c4h attribute: r/wc default value: 00h size: 8 bits function level reset:no . 14.1.39 sp scratch pad register (sata?d31:f2) address offset: d0h attribute: r/w default value: 00000000h size: 32 bits . bit description 7:4 reserved 3 secondary slave trap (sst) ? r/wc. indicates that a trap occurred to the secondary slave device. 2 secondary master trap (spt) ? r/wc. indicates that a trap occurred to the secondary master device. 1 primary slave trap (pst) ? r/wc. indicates that a trap occurred to the primary slave device. 0 primary master trap (pmt) ? r/wc. indicates that a trap occurred to the primary master device. bit description 31:0 data (dt) ? r/w. this is a read/write register that is available for software to use. no hardware action is taken on this register. http://www..net/ datasheet pdf - http://www..net/ datasheet 525 sata controller registers (d31:f2) 14.1.40 bfcs?bist fis control/st atus register (sata?d31:f2) address offset: e0h ? e3h attribute: r/w, r/wc default value: 00000000h size: 32 bits bits description 31:16 reserved 15 port 5 bist fis initiate (p5bfi) ? r/w. when a rising edge is detected on this bit field, the ich10 initiates a bist fis to th e device on port 5, using the parameters specified in this register and the data sp ecified in bftd1 and bftd2. the bist fis will only be initiated if a device on port 5 is present and read y (not partial/slumber state). after a bist fis is successfully completed, soft ware must disable and re- enable the port using the pxe bits at offset 92h prior to attempting additional bist fiss or to return the ich10 to a normal operational mode. if the bist fis fails to complete, as indicated by the bff bit in the register, then software can clear then set the p5bfi bit to initiate another bist fis. this can be retried until the bist fis eventually completes successfully 14 port 4 bist fis initiate (p4bfi) ? r/w. when a rising edge is detected on this bit field, the ich10 initiates a bist fis to th e device on port 4, using the parameters specified in this register and the data sp ecified in bftd1 and bftd2. the bist fis will only be initiated if a device on port 4 is present and read y (not partial/slumber state). after a bist fis is successfully completed, soft ware must disable and re- enable the port using the pxe bits at offset 92h prior to attempting additional bist fiss or to return the ich10 to a normal operational mode. if the bist fis fails to complete, as indicated by the bff bit in the register, then software can clear then set the p4bfi bit to initiate another bist fis. this can be retried until the bist fis eventually completes successfully 13 port 3 bist fis initiate (p3bfi) ? r/w. when a rising edge is detected on this bit field, the ich10 initiates a bist fis to th e device on port 3, using the parameters specified in this register and the data sp ecified in bftd1 and bftd2. the bist fis will only be initiated if a device on port 3 is present and read y (not partial/slumber state). after a bist fis is successfully completed, soft ware must disable and re- enable the port using the pxe bits at offset 92h prior to attempting additional bist fiss or to return the ich10 to a normal operational mode. if the bist fis fails to complete, as indicated by the bff bit in the register, then software can clear then set the p3bfi bit to initiate another bist fis. this can be retried until the bist fis eventually completes successfully 12 port 2 bist fis initiate (p2bfi) ? r/w. when a rising edge is detected on this bit field, the ich10 initiates a bist fis to th e device on port 2, using the parameters specified in this register and the data sp ecified in bftd1 and bftd2. the bist fis will only be initiated if a device on port 2 is present and read y (not partial/slumber state). after a bist fis is successfully completed, soft ware must disable and re- enable the port using the pxe bits at offset 92h prior to attempting additional bist fises or to return the ich10 to a normal operational mode. if the bist fis fails to complete, as indicated by the bff bit in the register, then software can clear then set the p2bfi bit to initiate another bist fis. this can be retried until the bist fis eventually completes successfully 11 bist fis successful (bfs) ? r/wc. 0 = software clears this bi t by writing a 1 to it. 1 = this bit is set any time a bist fis transmitted by ich10 receives an r_ok completion status from the device. note: this bit must be cleared by softwa re prior to initiating a bist fis. http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 526 datasheet 10 bist fis failed (bff) ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = this bit is set any time a bist fis transmitted by ich10 receives an r_err completion status from the device. note: this bit must be cleared by softwa re prior to initiating a bist fis. 9 port 1 bist fis initiate (p1bfi) ? r/w. when a rising edge is detected on this bit field, the ich10 initiates a bist fis to th e device on port 1, using the parameters specified in this register and the data sp ecified in bftd1 and bftd2. the bist fis will only be initiated if a device on port 1 is present and read y (not partial/slumber state). after a bist fis is successfully completed, software must disable and re- enable the port using the pxe bits at offset 92h prior to attempting additional bist fises or to return the ich10 to a normal operational mode. if the bist fis fails to complete, as indicated by the bff bit in the register, th en software can clear then set the p1bfi bit to initiate another bist fis. this can be retried until the bist fis eventually completes successfully 8 port 0 bist fis initiate (p0bfi) ? r/w. when a rising edge is detected on this bit field, the ich10 initiates a bist fis to th e device on port 0, using the parameters specified in this register and the data sp ecified in bftd1 and bftd2. the bist fis will only be initiated if a device on port 0 is present and read y (not partial/slumber state). after a bist fis is successfully completed, software must disable and re- enable the port using the pxe bits at offset 92h prior to attempting additional bist fises or to return the ich10 to a normal operational mode. if the bist fis fails to complete, as indicated by the bff bit in the register, th en software can clear then set the p0bfi bit to initiate another bist fis. this can be retried until the bist fis eventually completes successfully 7:2 bist fis parameters (bfp) ? r/w. these 6 bits form the contents of the upper 6 bits of the bist fis pattern definition in any bist fis transmitted by the ich10. this field is not port specific ? its contents will be used for any bist fis initiated on port 0, port 1, port 2 or port 3. the specific bit definitions are: bit 7: t ? far end transmit mode bit 6: a ? align bypass mode bit 5: s ? bypass scrambling bit 4: l ? far end retimed loopback bit 3: f ? far end analog loopback bit 2: p ? primitive bit for use with transmit mode 1:0 reserved bits description http://www..net/ datasheet pdf - http://www..net/ datasheet 527 sata controller registers (d31:f2) 14.1.41 bftd1?bist fis transmit data1 register (sata?d31:f2) address offset: e4h ? e7h attribute: r/w default value: 00000000h size: 32 bits 14.1.42 bftd2?bist fis transmit data2 register (sata?d31:f2) address offset: e8h ? ebh attribute: r/w default value: 00000000h size: 32 bits bits description 31:0 bist fis transmit data 1 ? r/w. the data programmed into this register will form the contents of the second dword of any bist fis initiated by the ich10. this register is not port specific ? its contents will be used for bist fis initiated on any port. although the 2nd and 3rd dws of the bist fis are only meaningful when the ?t? bit of the bist fis is set to indicate ?far-end transmit mode?, this register?s contents will be transmitted as the bist fis 2nd dw regardless of whether or not the ?t? bit is indicated in the bfcs register (d31:f2:e0h). bits description 31:0 bist fis transmit data 2 ? r/w. the data programmed into this register will form the contents of the third dword of any bist fis initiated by the ich10. this register is not port specific ? its contents will be used for bist fis initiated on any port. although the 2nd and 3rd dws of the bist fis are only meaningful when the ?t? bit of the bist fis is set to indicate ?far-end transmit mode?, this register?s contents will be transmitted as the bist fis 3rd dw regardless of whether or not the ?t? bit is indicated in the bfcs register (d31:f2:e0h). http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 528 datasheet 14.2 bus master ide i/ o registers (d31:f2) the bus master ide function uses 16 bytes of i/o space, allocated via the bar register, located in device 31:function 2 configuration space, offset 20h. all bus master ide i/o space registers can be accessed as byte, word, or dword quantities. reading reserved bits returns an indeterminate, inconsistent va lue, and writes to reserved bits have no affect (but should not be attempted). these registers are only used for legacy operation. software must not use these registers when running ahci. all i/o registers are reset by function level reset. the description of the i/o registers is shown in ta b l e 1 4 - 2 . table 14-2. bus master ide i/o register address map bar+ offset mnemonic register default type 00 bmicp command register primary 00h r/w 01 ? reserved ? ro 02 bmisp bus master ide status register primary 00h r/w, r/ wc, ro 03 ? reserved ? ro 04?07 bmidp bus master ide descriptor table pointer primary xxxxxxxx h r/w 08 bmics command register secondary 00h r/w 09 ? reserved ? ro 0ah bmiss bus master ide status register secondary 00h r/w, r/ wc, ro 0bh ? reserved ? ro 0ch? 0fh bmids bus master ide descriptor table pointer secondary xxxxxxxx h r/w 10h air ahci index register 00000000 h r/w, ro 14h aidr ahci index data register xxxxxxxx h r/w http://www..net/ datasheet pdf - http://www..net/ datasheet 529 sata controller registers (d31:f2) 14.2.1 bmic[p,s]?bus master id e command register (d31:f2) address offset: primary: bar + 00h attribute: r/w secondary: bar + 08h default value: 00h size: 8 bits bit description 7:4 reserved. returns 0. 3 read / write control (r/wc) ? r/w. this bit sets the di rection of the bus master transfer: this bit must not be changed wh en the bus master function is active. 0 = memory reads 1 = memory writes 2:1 reserved. returns 0. 0 start/stop bus master (start) ? r/w. 0 = all state information is lost when this bit is cleared. master mode operation cannot be stopped and then resumed. if this bit is reset while bus master operation is still active (i.e., the bus master ide active bit (d31:f2:bar + 02h, bit 0) of the bus master ide status register for that ide channel is set) and the drive has not yet finished its data transfer (the interrupt bi t in the bus master id e status register for that ide channel is not set), the bus master command is said to be aborted and data transferred from the drive may be discarded instead of being written to system memory. 1 = enables bus master operation of the controller. bus master operation does not actually start unless the bus master enable bit (d31:f1:04h, bit 2) in pci configuration space is also set. bus master operation begins when this bit is detected changing from 0 to 1. the controller will transfer data between the ide device and memory only when this bit is set. master operation can be halted by writing a 0 to this bit. note: this bit is intended to be cleared by software after the data transfer is completed, as indicated by either the bu s master ide active bit being cleared or the interrupt bit of the bus master ide status register fo r that ide channel being set, or both. hardware does not clea r this bit automatically. if this bit is cleared to 0 prior to the dma data transfer being initiated by the drive in a http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 530 datasheet 14.2.2 bmis[p,s]?bus master id e status register (d31:f2) address offset: primary: bar + 02h attribute: r/w, r/wc, ro secondary: bar + 0ah default value: 00h size: 8 bits bit description 7 prd interrupt status (prdis) ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = this bit is set when the host controller execution of a prd that has its prd_int bit set. 6 drive 1 dma capable ? r/w. 0 = not capable. 1 = capable. set by device dependent code (b ios or device driver ) to indicate that drive 1 for this channel is capable of dm a transfers, and that the controller has been initialized for optimu m performance. the intel ? ich10 does not use this bit. it is intended for systems that do not attach bmide to the pci bus. 5 drive 0 dma capable ? r/w. 0 = not capable 1 = capable. set by device dependent code (b ios or device driver ) to indicate that drive 0 for this channel is capable of dm a transfers, and that the controller has been initialized for optimum performance. the ich10 does not use this bit. it is intended for systems that do no t attach bmide to the pci bus. 4:3 reserved. returns 0. 2 interrupt ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = set when a device fis is received with the ?i? bit set, provided that software has not disabled interrupts via the ien bit of the device control register (see chapter 5 of the serial ata specification , revision 1.0a). 1 error ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = this bit is set when the controller encoun ters a target abort or master abort when transferring data on pci. 0 bus master ide active (act) ? ro. 0 = this bit is cleared by the ich10 when th e last transfer for a region is performed, where eot for that region is set in the regi on descriptor. it is also cleared by the ich10 when the start bus master bit (d31:f2:bar+ 00h, bit 0) is cleared in the command register. when this bi t is read as a 0, all data transferred from the drive during the previous bus master command is visible in system memory, unless the bus master command was aborted. 1 = set by the ich10 when the start bit is written to the command register. http://www..net/ datasheet pdf - http://www..net/ datasheet 531 sata controller registers (d31:f2) 14.2.3 bmid[p,s]?bus master id e descriptor table pointer register (d31:f2) address offset: primary: bar + 04h?07h attribute: r/w secondary: bar + 0ch ? 0fh default value: all bits undefined size: 32 bits 14.2.4 air?ahci index register (d31:f2) address offset: primary: bar + 10h attribute: r/w default value: 00000000h size: 32 bits this register is available only when scc is not 01h. 14.2.5 aidr?ahci index da ta register (d31:f2) address offset: primary: bar + 14h attribute: r/w default value: all bits undefined size: 32 bits this register is available only when scc is not 01h. bit description 31:2 address of descriptor table (addr) ? r/w. the bits in this field correspond to bits [31:2] of the memory location of the physic al region descriptor (prd). the descriptor table must be dword-aligned. the descriptor table must not cross a 64-k boundary in memory. 1:0 reserved bit description 31:11 reserved 10:2 index (index) ? r/w : this index register is used to select the dword offset of the memory mapped ahci register to be access ed. a dword, word or byte access is specified by the active byte enables of the i/o access to the data register. 1:0 reserved bit description 31:0 data (data) ? r/w : this data register is a ?window? through which data is read or written to the ahci memory mapped registers. a read or write to this data register triggers a corresponding read or write to the memory mapped register pointed to by the index register. the index re gister must be setup prior to the read or write to this data register. note that a physical register is not actually implemented as the data is actually stored in the memory mapped registers. since this is not a physical register, the ?default? value is the same as the default value of the register pointed to by index. http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 532 datasheet 14.3 serial ata index/data pair superset registers all of these i/o registers are in the core we ll. they are exposed only when scc is 01h (i.e., ide programming interface). these are index/data pair registers that are used to access the serialata superset registers (serialata status, serialata cont rol and serialata error). the i/o space for these registers is allocated through sidpba. locations with offset from 08h to 0fh are reserved for future expansion. software-write operations to the reserved locations will have no effect while software-read operatio ns to the reserved locations will return 0. 14.3.1 sindx ? serial ata index (d31:f2) address offset: sidpba + 00h attribute: r/w default value: 00000000h size: 32 bits 14.3.2 sdata ? serial ata data (d31:f2) address offset: sidpba + 04h attribute: r/w default value: 00000000h size: 32 bits offset mnemonic register 00h?03h sindex serial ata index 04h?07h sdata serial ata data 08h?0ch ? reserved 0ch?0fh ? reserved bit description 31:16 reserved 15.8 port index (pidx) - r/w: this index field is used to specify the port of the sata controller at which the po rt-specific ssts, sctl, and serr registers are located. 00h = primary master (port 0) 01h = primary slave (port 2) 02h = secondary master (port 1) 03h = secondary slave (port 3) all other values are reserved. 7:0 register index (ridx) - r/w: this index field is used to specify one out of three registers currently bein g indexed into. these three regist ers are the serial ata superset sstatus, scontrol and serror memory regist ers and are port specific, hence for this sata controller, there are four se ts of these registers. refer to section 14.4.3.10 , section 14.4.3.11 , and section 14.4.3.12 for definitions of the sstatus, scontrol, and serror registers. 00h = ssts 01h = sctl 02h = serr all other values are reserved. bit description 31:0 data (data) - r/w: this data register is a ?win dow? through which data is read or written to from the register pointed to by th e serial ata index (sindx) register above. note that a physical register is not actually implemented as the data is actually stored in the memory mapped registers. since this is not a physical register, the ?default? value is the same as the default value of the register pointed to by sindx.ridx field. http://www..net/ datasheet pdf - http://www..net/ datasheet 533 sata controller registers (d31:f2) 14.3.2.1 pxssts?serial ata status register (d31:f2) address offset: attribute: ro default value: 00000000h size: 32 bits sdata when sindx.ridx is 00h. this is a 32-b it register that conveys the current state of the interface and host. the ich10 updates it continuously and asynchronously. when the ich10 transmits a comreset to the device , this register is updated to its reset values. bit description 31:12 reserved 11:8 interface power management (ipm) ? ro . indicates the current interface state: all other values reserved. 7:4 current interface speed (spd) ? ro. indicates the negotiated interface communication speed. all other values reserved. ich10 supports generation 1 communication rates (1.5 gb/s) and gen 2 rates (3.0 gb/s). 3:0 device detection (det) ? ro . indicates the interface de vice detection and phy state: all other values reserved. value description 0h device not present or communication not established 1h interface in active state 2h interface in partial power management state 6h interface in slumber power management state value description 0h device not present or communication not established 1h generation 1 communication rate negotiated 2h generation 2 communication rate negotiated value description 0h no device de tected and phy communication not established 1h device presence detected but phy communication not established 3h device presence detected and phy communication established 4h phy in offline mode as a result of the interface being disabled or running in a bist loopback mode http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 534 datasheet 14.3.2.2 pxsctl ? serial ata control register (d31:f2) address offset: attribute: r/w, ro default value: 00000004h size: 32 bits sdata when sindx.ridx is 01h. this is a 32-bit read-write register by which software controls sata capabilities. writes to the sc ontrol register result in an action being taken by the ich10 or the interface. reads from the register return the last value written to it. bit description 31:20 reserved 19:16 port multiplier port (pmp) ? ro . this field is not used by ahci. 15:12 select power management (spm) ? ro. this field is not used by ahci. 11:8 interface power management transitions allowed (ipm) ? r/w . indicates which power states the ich10 is allowed to transition to: all other values reserved 7:4 speed allowed (spd) ? r/w. indicates the highest al lowable speed of the interface. this speed is limited by the ca p.iss (abar+00h:bit 23:20) field. all other values reserved. ich10 supports generation 1 communication rates (1.5 gb/s) and gen 2 rates (3.0 gb/s). 3:0 device detection initialization (det) ? r/w . controls the ich10?s device detection and interface initialization. all other values reserved. when this field is written to a 1h, the ich10 initiates comreset and starts the initialization process. when the initialization is complete, this field shall remain 1h until set to another value by software. this field may only be change d to 1h or 4h when pxcmd.st is 0. changing this field while the ich10 is running re sults in undefined behavior. value description 0h no interface restrictions 1h transitions to the partial state disabled 2h transitions to the slumber state disabled 3h transitions to both partial and slumber states disabled value description 0h no speed negotiation restrictions 1h limit speed negotiation to generation 1 communication rate 2h limit speed negotiation to generation 2 communication rate value description 0h no device detection or initialization action requested 1h perform interface communication initialization sequence to establish communication. this is functionally equivalent to a hard reset and results in the interface bein g reset and communications re- initialized 4h disable the serial ata interface and put phy in offline mode http://www..net/ datasheet pdf - http://www..net/ datasheet 535 sata controller registers (d31:f2) 14.3.2.3 pxserr?serial ata error register (d31:f2) address offset: attribute: r/wc default value: 00000000h size: 32 bits sdata when sindx.ridx is 02h. bits 26:16 of this register contains diagnostic error information for use by diagnostic software in validating correct operation or isolating failure modes. bits 11:0 contain error information used by host software in determining the appropriate response to the error condition. if one or more of bits 11:8 of this register are set, the controller will stop the current transfer. bit description 31:27 reserved 26 exchanged (x) : when set to one this bit indicates that a change in device presence has been detected since the last time this bit was cleared. this bit sh all always be set to 1 anytime a cominit signal is received. th is bit is reflected in the p0is.pcs bit. 25 unrecognized fis type (f) : indicates that one or more fiss were received by the transport layer with good crc, but had a type field that was not recognized. 24 transport state transition error (t) : indicates that an e rror has occurred in the transition from one state to another within the transport layer since the last time this bit was cleared. 23 transport state transition error (t) : indicates that an e rror has occurred in the transition from one state to another within the transport layer since the last time this bit was cleared. 22 handshake (h) : indicates that one or more r_err handshake response was received in response to frame transmission. such errors may be the result of a crc error detected by the recipient, a disparity or 8b/ 10b decoding error, or other error condition leading to a negative handshake on a transmitted frame. 21 crc error (c) : indicates that one or more crc e rrors occurred with the link layer. 20 disparity error (d) : this field is not used by ahci. 19 10b to 8b decode error (b) : indicates that one or more 10b to 8b decoding errors occurred. 18 comm wake (w) : indicates that a comm wake si gnal was detected by the phy. 17 phy internal error (i) : indicates that the phy dete cted some internal error. 16 phyrdy change (n) : when set to 1 this bit indicates that the internal phyrdy signal changed state since the last time this bit was cleared. in the ich10, this bit will be set when phyrdy changes from a 0 -> 1 or a 1 -> 0. the state of this bit is then reflected in the pxis.prcs interrupt stat us bit and an interrupt will be generated if enabled. software clears this bi t by writing a 1 to it. 15:12 reserved 11 internal error (e) : the sata controller failed due to a master or target abort when attempting to access system memory. 10 protocol error (p) : a violation of the serial ata protocol was detected. note: the ich10 does not set this bit for all protocol violations that may occur on the sata link. http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 536 datasheet 14.4 ahci registers (d31:f2) note: these registers are ahci-specific and availabl e when the ich10 is properly configured. the serial ata status, control, and error re gisters are special exceptions and may be accessed on all ich10 components if properly configured; see section 14.3 for details. the memory mapped registers within the sata controller exist in non-cacheable memory space. additionally, locked accesses ar e not supported. if software attempts to perform locked transactions to the registers, indeterminate results may occur. register accesses shall have a maximum size of 64-bits; 64-bit access must not cross an 8-byte alignment boundary. all memory registers are reset by function level reset unless specified otherwise. the registers are broken into two sections ? generic host control and port control. the port control registers are the same for all ports, and there are as many registers banks as there are ports. 9 persistent communication or data integrity error (c) : a communication error that was not recovered occurred that is expected to be pers istent. persistent communications errors may arise from faulty interconne ct with the device, from a device that has been removed or has failed, or a number of other causes. 8 transient data integrity error (t) : a data integrity error occurred that was not recovered by the interface. 7:2 reserved. 1 recovered communications error (m) : communications betw een the device and host was temporarily lost but was re-established. this can arise from a device temporarily being removed, from a temporar y loss of phy synchronization, or from other causes and may be derived from the phynrdy signal between the phy and link layers. 0 recovered data integrity error (i) : a data integrity error occurred that was recovered by the interface through a retr y operation or other recovery action. bit description table 14-3. ahci register address map abar + offset mnemonic register 00?1fh ghc generic host control 20h?ffh ? reserved 100h?17fh p0pcr port 0 port control registers 180h?1ffh p1pcr port 1 port control registers 200h?27fh p2pcr port 2 port control registers 280h?2ffh p3pcr port 3 port control registers 300h?37fh p4pcr port 4 port control registers 380h?3ffh p5pcr port 5 port control registers http://www..net/ datasheet pdf - http://www..net/ datasheet 537 sata controller registers (d31:f2) 14.4.1 ahci generic host co ntrol registers (d31:f2) 14.4.1.1 cap?host capabilities register (d31:f2) address offset: abar + 00h?03h attribute: r/wo, ro default value: ff22ffc2h (consumer only) size: 32 bits ff22ff45h (corporate only) function level reset: no all bits in this register that are r/wo are reset only by pltrst#. table 14-4. generic host cont roller register address map abar + offset mnemonic register default type 00?03 cap host capabilities ff22ffc2h r/wo, ro 04?07 ghc global ich10 control 00000000h r/w, ro 08?0bh is interrupt status 00000000h r/wc 0ch?0fh pi ports implemented 00000000h r/wo, ro 10h-13h vs ahci version 00010200h ro 14h-17h ccc_ctl command completion coalescing control 00010121h r/w, ro 18h-1bh ccc_ports command completion coalescing ports 00000000h r/w 1ch-1fh em_loc enclosure management location 01000002h ro 20h-23h em_ctrl enclosure management control 07010000h r/w, r/wo, ro a0h-a3h vsp vendor specific 00000000h ro, r/wo bit description 31 supports 64-bit addressing (s64a) ? ro. indicates that the sata controller can access 64-bit data structures. the 32-bi t upper bits of the port dma descriptor, the prd base, and each prd entry are read/write. 30 supports command queue acceleration (scqa) ? ro. hardwired to 1 to indicate that the sata co ntroller supports sata command queuing via the dma setup fis. the intel ? ich10 handles dma setup fises natively, and can handle auto-activate optimization through that fis. 29 supports snotification regist er (ssntf): ? ro. the ich10 sata controller does not support the snotification register. 28 supports interlock switch (sis) ? r/wo. indicates whether the sata controller supports interlock switches on its ports for use in hot plug operations. this value is loaded by platform bios prior to os initialization. if this bit is set, bios must also map the satagp pins to the sata controller through gpio space. 27 supports staggered spin-up (sss) ? r/wo. indicates whether the sata controller supports staggere d spin-up on its ports, for use in balancing power spikes. this value is loaded by platform bios prior to os initialization. 0 = staggered spin-up not supported. 1 = staggered spin-up supported. http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 538 datasheet 26 supports aggressive link power management (salp) ? r/wo. 0 = software shall treat the pxcmd.alpe and pxcmd.asp bits as reserved. 1 = the sata controller supports auto-gener ating link requests to the partial or slumber states when there are no commands to process. 25 supports activity led (sal) ? ro. indicates that the sata controller supports a single output pin (sataled#) which indicates activity. 24 supports command list override (sclo) ? r/wo. when set to 1, indicates that the controller supports the pxcmd.clo bit and it's associat ed function. when cleared to 0, the controller is not capabl e of clearing the bsy and drq bits in the status register in order to issue a software reset if th ese bits are still set from a previous operation. 23:20 interface speed support (iss) ? r/wo. indicates the maximum speed the sata controller can support on its ports. 2h =3.0 gb/s. 19 supports non-zero dma offsets (snzo) ? ro . reserved, as per the ahci revision 1.2 specification 18 supports ahci mode only (sam) ? ro. the sata controller may optionally support ahci access mechanism only. 0 = sata controller supports both ide and ahci modes 1 = sata controller supports ahci mode only 17 supports port multiplier (pms) ? r/wo. ich10 does not support port multiplier. note: this bit must be set to 0. port mu ltiplier is not supported by ich10. 16 reserved 15 pio multiple drq block (pmd) ? ro. the sata controller supports pio multiple drq command block 14 slumber state capable (ssc) ? r/wo. the sata controller supports the slumber state. 13 partial state capable (psc) ? r/wo. the sata controller supports the partial state. 12:8 number of command slots (ncs) ? ro. hardwired to 1fh to indicate support for 32 slots. 7 (consumer only) command completion coalescing supported (cccs) ? r/wo. 0 = command completion coalescing not supported 1 = command completion coalescing supported 7 (corporate only) command completion coalescing supported (cccs) ? ro. command completion coalescing is not supported. reads to this bit return 0. 6 enclosure management supported (ems) ? r/wo. 0 = enclosure management not supported 1 = enclosure management supported 5 supports external sata (sxs) ? r/wo. 0 = external sata is not supported on any ports 1 = external sata is supported on one or more ports when set, sw can examine each sata port?s command register (pxcmd) to determine which port is routed externally. 4:0 number of ports (nps) ? ro. hardwired to 5h to indicate support for 6 ports. note that the number of ports indicated in this field may be more than the number of ports indicated in the pi (abar + 0ch) register. bit description http://www..net/ datasheet pdf - http://www..net/ datasheet 539 sata controller registers (d31:f2) 14.4.1.2 ghc?global ich10 control register (d31:f2) address offset: abar + 04h?07h attribute: r/w, ro default value: 00000000h size: 32 bits bit description 31 ahci enable (ae) ? r/w. when set, indicates that an ahci driver is loaded and the controller will be talked to via ahci mech anisms. this can be us ed by an ich10 that supports both legacy mechanisms (such as sff-8038i) and ahci to know when the controller will not be talked to as legacy. 0 = software will communicate with the ich10 using legacy mechanisms. 1 = software will communicate with the ich1 0 using ahci. the ich10 will not have to allow command processing via both ahci and legacy mechanisms. software shall set this bit to 1 before acce ssing other ahci registers. 30:3 reserved 2 msi revert to single message (mrsm) ? ro: when set to 1 by hardware, indicates that the host controller requ ested more than one msi vector but has reverted to using the first vector only. when this bit is cleare d to '0', the controller has not reverted to single msi mode (i.e. hardware is already in single msi mode, software has allocated the number of messages requested, or hardwa re is sharing interrupt vectors if mc.mme < mc.mmc). "mc.msie = '1' (msi is enabled) "mc.mmc > 0 (multiple messages requested) "mc.mme > 0 (more than one message allocated) "mc.mme!= mc.mmc (messages allocate d not equal to number requested) when this bit is set to 1, single msi mo de operation is in use and software is responsible for clearing bits in th e is register to clear interrupts. this bit shall be cleared to 0 by hardware when any of the four conditions stated is false. this bit is also cleared to 0 when mc.msie = 1 and mc.mme = 0h. in this case, the hardware has been programmed to use si ngle msi mode, and is not "reverting" to that mode. for ich10, the controller shall always reve rt to single msi mode when the number of vectors allocated by the host is less than the number requested. this bit is ignored when ghc.hr = 1. 1 interrupt enable (ie) ? r/w. this global bit enab les interrupts from the ich10. 0 = all interrupt sources fr om all ports are disabled. 1 = interrupts are allowed from the ahci controller. 0 controller reset (hr) ? r/w. resets ich10 ahci controller. 0 = no effect 1 = when set by sw, this bit causes an intern al reset of the ich10 ahci controller. all state machines that relate to data transfers and queuing return to an idle condition, and all ports are re-initialized via comreset. note: for further details, cons ult section 12.3.3 of the serial ata advanced host controller interface specification. http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 540 datasheet 14.4.1.3 is?interrupt status register (d31:f2) address offset: abar + 08h ? 0bh attribute: r/wc default value: 00000000h size: 32 bits this register indicates which of the ports with in the controller have an interrupt pending and require service. bit description 31:7 reserved. returns 0. 6 coalescing interrupt pending status (cips) ? r/wc . 0 = no interrupt pending. 1 = a command completion coalesci ng interrupt has been generated. 5 interrupt pending status port[5] (ips[5]) ? r/wc . 0 = no interrupt pending. 1 = port 5 has an interrupt pending. softwa re can use this info rmation to determine which ports require serv ice after an interrupt. 4 interrupt pending status port[4] (ips[4]) ? r/wc . 0 = no interrupt pending. 1 = port 4 has an interrupt pending. softwa re can use this info rmation to determine which ports require serv ice after an interrupt. 3 interrupt pending status port[3] (ips[3]) ? r/wc . 0 = no interrupt pending. 1 = port 3 has an interrupt pending. softwa re can use this info rmation to determine which ports require serv ice after an interrupt. 2 interrupt pending status port[2] (ips[2]) ? r/wc 0 = no interrupt pending. 1 = port 2 has an interrupt pending. softwa re can use this info rmation to determine which ports require serv ice after an interrupt. 1 interrupt pending status port[1] (ips[1]) ? r/wc . 0 = no interrupt pending. 1 = port 1has an interrupt pending. softwa re can use this info rmation to determine which ports require serv ice after an interrupt. 0 interrupt pending status port[0] (ips[0]) ? r/wc . 0 = no interrupt pending. 1 = port 0 has an interrupt pending. softwa re can use this info rmation to determine which ports require serv ice after an interrupt. http://www..net/ datasheet pdf - http://www..net/ datasheet 541 sata controller registers (d31:f2) 14.4.1.4 pi?ports implemented register (d31:f2) address offset: abar + 0ch?0fh attribute: r/wo, ro default value: 00000000h size: 32 bits function level reset: no this register indicates which ports are exposed to the ich10. it is loaded by platform bios. it indicates which ports that the device supports are available for software to use. for ports that are not available, software must not read or write to registers within that port. bit description 31:6 reserved. returns 0. 5 ports implemented port 5 (pi5) ? r/wo. 0 = the port is not implemented. 1 = the port is implemented. this bit is read-only ?0? if map.sc = ?0? or scc = ?01h?. 4 ports implemented port 4 (pi4) ? r/wo. 0 = the port is not implemented. 1 = the port is implemented. this bit is read-only ?0? if map.sc = ?0? or scc = ?01h?. 3 ports implemented port 3 (pi3) ? r/wo. 0 = the port is not implemented. 1 = the port is implemented. 2 ports implemented port 2 (pi2) ? r/wo. 0 = the port is not implemented. 1 = the port is implemented. 1 ports implemented port 1 (pi1) ? r/wo. 0 = the port is not implemented. 1 = the port is implemented. 0 ports implemented port 0 (pi0) ? r/wo . 0 = the port is not implemented. 1 = the port is implemented. http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 542 datasheet 14.4.1.5 vs?ahci version (d31:f2) address offset: abar + 10h?13h attribute: ro default value: 00010200h size: 32 bits this register indicates the major and minor ve rsion of the ahci specification. it is bcd encoded. the upper two bytes represent th e major version number, and the lower two bytes represent the minor version numbe r. example: version 3.12 would be represented as 00030102h. the current version of the specification is 1.20 (00010200h). 14.4.1.6 ccc_ctl?command completion coalescing control register (d31:f2) address offset: abar + 14h?17h attribute: r/w, ro default value: 00010131h size: 32 bits this register is used to configure the command coalescing feature. this register is reserved if command coalescing is not supported (cap_cccs = ?0?). bit description 31:16 major version number (mjr) ? ro. indicates the major version is 1 15:0 minor version number (mnr) ? ro. indicates the minor version is 20. bit description 31:16 timeout value (tv) ? r/w. the timeout value is specified in 10 microsecond intervals. hbaccc_timer is loaded with th is timeout value. hbaccc_timer is only decremented when commands ar e outstanding on the selected ports. the controller will signal a ccc interrupt when hba ccc_timer has decremented to ?0?. the hbaccc_timer is reset to the timeout value on the assertion of each ccc interrupt. a timeout value of 0 is invalid. 15:8 command completions (cc) ? r/w. specifies the number of command completions that ar e necessary to cause a ccc inte rrupt. the controller has an internal command completion co unter, hbaccc_commandscomplete. hbaccc_commandscomplete is incremented by one each time a selected port has a command completion. when hbaccc_command scomplete is equal to the command completions value, a ccc interrupt is sign aled. the internal command completion counter is reset to ?0? on the assertion of each ccc interrupt. 7:3 interrupt (int) ? ro. specifies the interrupt used by the ccc feature. this interrupt must be marked as unused in the ahci ports implemented memory register by the corresponding bit being set to ?0?. thus, the ccc_interrupt corresponds to the interrupt for an unimplemente d port on the controller. when a ccc interrupt occurs, the is[int] bit shall be asserted to ?1? rega rdless of whether pirq interrupt or msi is used. note that in msi, cc interru pt may share an interrupt ve ctor with other ports. for example, if the number of message allocated is 4, then ccc inte rrupt share interrupt vector 3 along with port 3, 4, and 5 but is[6] shall get set. 2:1 reserved 0 enable (en) ? r/w . 0 = the command completion coalescing feat ure is disabled and no ccc interrupts are generated 1 = the command completion coalescing feature is enabled and ccc interrupts may be generated based on timeout or command completion conditions. software shall only change the contents of the tv and cc fields wh en en is cleared to '0'. on transition of this bit from '0' to '1 ', any updated values for the tv and cc fields shall take effect. http://www..net/ datasheet pdf - http://www..net/ datasheet 543 sata controller registers (d31:f2) 14.4.1.7 ccc_ports?command completion coalescing ports register (d31:f2) address offset: abar + 18h?1bh attribute: r/w default value: 00000000h size: 32 bits this register is used to specify the ports that are coalesced as part of the ccc feature when ccc_ctl.en = ?1?. this register is reserved if command coalescing is not supported (cap_cccs = ?0?). 14.4.1.8 em_loc?enclosure management location register (d31:f2) address offset: abar + 1ch?1fh attribute: ro default value: 01000002h size: 32 bits this register identifies the location and size of the enclosure management message buffer. this register is reserved if encl osure management is not supported (i.e., cap.ems = 0). bit description 31:0 ports (prt) ? r/w. 0 = the port is not part of the co mmand completion coalescing feature. 1 = the corresponding port is part of th e command completion coalescing feature. bits set to ?1? in this register must also have the corresponding bit set to ?1? in the ports implemented register. bits set to '1' in this register must also have the corresponding bit set to '1' in the ports implemented re gister. an updated value for this fi eld shall take effect within one timer increment (1 millisecond). bit description 31:16 offset (ofst) ? ro. the offset of the message buffer in dwords from the beginning of the abar. 15:0 buffer size (sz) ? ro. specifies the size of the transmit message buffer area in dwords. the ich10 sata controller only supports transmit buffer. a value of ?0? is invalid. http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 544 datasheet 14.4.1.9 em_ctrl?enclosure management control register (d31:f2) address offset: abar + 20h?23h attribute: r/w, r/wo, ro default value: 07010000h size: 32 bits this register is used to control and obtain status for the enclosure management interface. this register includes informatio n on the attributes of the implementation, enclosure management messages supported, the status of the interface, whether any message are pending, and is used to initiate sending messages. this register is reserved if enclosure management is not supported (cap_ems = ?0?). bit description 31:27 reserved 26 activity led hardware driven (attr.alhd) ? r/wo. 1 = the sata controller drives the activity led for the led message type in hardware and does not utilize software for this led. the host controller does no t begin transmitting the hard ware based activity signal until after software has written ctl.tm=1 after a reset condition. 25 transmit only (attr.xmt) ? ro. 0 = the sata controller supports tr ansmitting and re ceiving messages. 1 = the sata controller only supports transmitting messages and does not support receiving messages. 24 single message buffer (attr.smb) ? ro. 0 = there are separate receiv e and transmit buffers such that unsolicited messages could be supported. 1 = the sata controller has one message bu ffer that is shared for messages to transmit and messages received. unsolici ted receive messages are not supported and it is software?s responsibility to manage access to this buffer. 23:20 reserved 19 sgpio enclosure management messages (supp.sgpio): ? ro. 1 = the sata controller supports the sg pio register interface message type. 18 ses-2 enclosure management messages (supp.ses2): ? ro. 1 = the sata controller suppo rts the ses-2 message type. 17 saf-te enclosure management messages (supp.safte): ? ro. 1 = the sata controller suppo rts the saf-te message type. 16 led message types (supp.led): ? ro. 1 = the sata controller su pports the led message type. 15:10 reserved 9 reset (rst): ? r/w. 0 = a write of ?0? to this bit by software will have no effect. 1 = when set by software, the sata controll er shall reset all enclosure management message logic and take all appropriate rese t actions to ensure messages can be transmitted / received after the reset. after the sata contro ller completes the reset operation, the sa ta controller shall set the value to ?0?. 8 transmit message (ctl.tm): ? r/w. 0 = a write of ?0? to this bit by software will have no effect. 1 = when set by software, the sata controll er shall transmit th e message contained in the message buffer. when the message is completely sent, the sata controller shall set the value to ?0?. software shall not change th e contents of the message bu ffer while ctl.tm is set to '1'. 7:1 reserved 0 message received (sts.mr): ? ro. message received is not supported in ich10. http://www..net/ datasheet pdf - http://www..net/ datasheet 545 sata controller registers (d31:f2) 14.4.2 vendor specific registers (d31:f2) 14.4.2.1 vsp?vendor specific (d31:f2) address offset: abar + a0h?a3h attribute: ro, rwo default value: 00000000h size: 32 bits 14.4.3 port registers (d31:f2) ports not available will result in the corresponding port dma register space being reserved. the controller shall ignore writes to the reserved space on write cycles and shall return ?0? on read cycle a ccesses to the reserved location. bit description 31:1 reserved 0 supports low power device detection (slpd)? rwo indicates whether sata powe r management and device hot (un)pulg is supported. 0 = not supported. 1 = supported. table 14-5. port [5:0] dma register address map (sheet 1 of 3) abar + offset mnemonic register 100h?103h p0clb port 0 command list base address 104h?107h p0clbu port 0 command li st base address upper 32-bits 108h?10bh p0fb port 0 fis base address 10ch?10fh p0fbu port 0 fis base address upper 32-bits 110h?113h p0is port 0 interrupt status 114h?117h p0ie port 0 interrupt enable 118h?11bh p0cmd port 0 command 11ch?11fh ? reserved 120h?123h p0tfd port 0 task file data 124h?127h p0sig port 0 signature 128h?12bh p0ssts port 0 serial ata status 12ch?12fh p0sctl port 0 serial ata control 130h?133h p0serr port 0 serial ata error 134h?137h p0sact port 0 serial ata active 138h?13bh p0ci port 0 command issue 13ch?17fh ? reserved 180h?183h p1clb port 1 command list base address 184h?187h p1clbu port 1 command li st base address upper 32-bits 188h?18bh p1fb port 1 fis base address 18ch?18fh p1fbu port 1 fis base address upper 32-bits 190h?193h p1is port 1 interrupt status 194h?197h p1ie port 1 interrupt enable 198h?19bh p1cmd port 1 command 19ch?19fh ? reserved 1a0h?1a3h p1tfd port 1 task file data 1a4h?1a7h p1sig port 1 signature http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 546 datasheet 1a8h?1abh p1ssts port 1 serial ata status 1ach?1afh p1sctl port 1 serial ata control 1b0h?1b3h p1serr port 1 serial ata error 1b4h?1b7h p1sact port 1 serial ata active 1b8h?1bbh p1ci port 1 command issue 1bch?1ffh ? reserved 200h?203h p2clb port 2 command list base address 204h?207h p2clbu port 2 command list base address upper 32-bits 208h?20bh p2fb port 2 fis base address 20ch?20fh p2fbu port 2 fis ba se address upper 32-bits 210h?213h p2is port 2 interrupt status 214h?217h p2ie port 2 interrupt enable 218h?21bh p2cmd port 2 command 21ch?21fh ? reserved 220h?223h p2tfd port 2 task file data 224h?227h p2sig port 2 signature 228h?22bh p2ssts port 2 serial ata status 22ch?22fh p2sctl port 2 serial ata control 230h?233h p2serr port 2 serial ata error 234h?237h p2sact port 2 serial ata active 238h?23bh p2ci port 2 command issue 23ch?27fh ? reserved 280h?283h p3clb port 3 command list base address 284h?287h p3clbu port 3 command list base address upper 32-bits 288h?28bh p3fb port 3 fis base address 28ch?28fh p3fbu port 3 fis ba se address upper 32-bits 290h?293h p3is port 3 interrupt status 294h?297h p3ie port 3 interrupt enable 298h?29bh p3cmd port 3 command 29ch?29fh ? reserved 2a0h?2a3h p3tfd port 3 task file data 2a4h?2a7h p3sig por t 3 signature 2a8h?2abh p3ssts port 3 serial ata status 2ach?2afh p3sctl port 3 serial ata control 2b0h?2b3h p3serr port 3 serial ata error 2b4h?2b7h p3sact port 3 serial ata active 2b8h?2bbh p3ci port 3 command issue 2bch?2ffh ? reserved 300h?303h p4clb port 4 command list base address 304h?307h p4clbu port 4 command list base address upper 32-bits 308h?30bh p4fb port 4 fis base address 30ch?30fh p4fbu port 4 fis ba se address upper 32-bits 310h?313h p4is port 4 interrupt status 314h?317h p4ie port 4 interrupt enable 318h?31bh p4cmd port 4 command 31ch?31fh ? reserved 320h?323h p4tfd port 4 task file data table 14-5. port [5:0] dma register address map (sheet 2 of 3) abar + offset mnemonic register http://www..net/ datasheet pdf - http://www..net/ datasheet 547 sata controller registers (d31:f2) 14.4.3.1 pxclb?port [5:0] comman d list base address register (d31:f2) address offset: port 0: abar + 100h attribute: r/w port 1: abar + 180h port 2: abar + 200h port 3: abar + 280h port 4: abar + 300h port 5: abar + 380h default value: undefined size: 32 bits 324h?327h p4sig port 4 signature 328h?32bh p4ssts port 4 serial ata status 32ch?32fh p4sctl port 4 serial ata control 330h?333h p4serr port 4 serial ata error 334h?337h p4sact port 4 serial ata active 338h?33bh p4ci port 4 command issue 33ch?37fh ? reserved 380h?383h p5clb port 5 command list base address 384h?387h p5clbu port 5 command li st base address upper 32-bits 388h?38bh p5fb port 5 fis base address 38ch?38fh p5fbu port 5 fis base address upper 32-bits 390h?393h p5is port 5 interrupt status 394h?397h p5ie port 5 interrupt enable 398h?39bh p5cmd port 5 command 39ch?39fh ? reserved 3a0h?3a3h p5tfd port 5 task file data 3a4h?3a7h p5sig port 5 signature 3a8h?3abh p5ssts port 5 serial ata status 3ach?3afh p5sctl port 5 serial ata control 3b0h?3b3h p5serr port 5 serial ata error 3b4h?3b7h p5sact port 5 serial ata active 3b8h?3bbh p5ci port 5 command issue 3bch?3ffh ? reserved table 14-5. port [5:0] dma register address map (sheet 3 of 3) abar + offset mnemonic register bit description 31:10 command list base address (clb) ? r/w . indicates the 32-bit base for the command list for this port. this base is used when fetching commands to execute. the structure pointed to by this a ddress range is 1 kb in length . this address must be 1-kb aligned as indicated by bi ts 31:10 being read/write. note that these bits are not reset on a controller reset. 9:0 reserved http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 548 datasheet 14.4.3.2 pxclbu?port [5:0] comm and list base address upper 32-bits register (d31:f2) address offset: port 0: abar + 104h attribute: r/w port 1: abar + 184h port 2: abar + 204h port 3: abar + 284h port 4: abar + 304h port 5: abar + 384h default value: undefined size: 32 bits 14.4.3.3 pxfb?port [5:0] fis ba se address register (d31:f2) address offset: port 0: abar + 108h attribute: r/w port 1: abar + 188h port 2: abar + 208h port 3: abar + 288h port 4: abar + 308h port 5: abar + 388h default value: undefined size: 32 bits 14.4.3.4 pxfbu?port [5:0] fis base address upper 32-bits register (d31:f2) address offset: port 0: abar + 10ch attribute: r/w port 1: abar + 18ch port 2: abar + 20ch port 3: abar + 28ch port 4: abar + 30ch port 5: abar + 38ch default value: undefined size: 32 bits bit description 31:0 command list base address upper (clbu) ? r/w . indicates the upper 32-bits for the command list base address for this po rt. this base is us ed when fetching commands to execute. note that these bits are not reset on a controller reset. bit description 31:8 fis base address (fb) ? r/w . indicates the 32-bit base for received fises. the structure pointed to by this address range is 256 bytes in length. this address must be 256-byte aligned, as indicated by bits 31:3 being read/write. note that these bits are not reset on a controller reset. 7:0 reserved bit description 31:0 command list base address upper (clbu) ? r/w . indicates the upper 32-bits for the received fis base for this port. note that these bits are not reset on a controller reset. http://www..net/ datasheet pdf - http://www..net/ datasheet 549 sata controller registers (d31:f2) 14.4.3.5 pxis?port [5:0] interru pt status register (d31:f2) address offset: port 0: abar + 110h attribute: r/wc, ro port 1: abar + 190h port 2: abar + 210h port 3: abar + 290h port 4: abar + 310h port 5: abar + 390h default value: 00000000h size: 32 bits bit description 31 cold port detect status (cpds) ? ro . cold presence detect is not supported. 30 task file error status (tfes) ? r/wc. this bit is set whenever the status register is updated by the device and the er ror bit (pxtfd.bit 0) is set. 29 host bus fatal error status (hbfs) ? r/wc . indicates that the intel ? ich10 encountered an erro r that it cannot recover from due to a bad software pointer. in pci, such an indication would be a target or master abort. 28 host bus data error status (hbds) ? r/wc . indicates that the ich10 encountered a data error (uncorrectable ecc / parity) when reading from or writing to system memory. 27 interface fatal error status (ifs) ? r/wc . indicates that the ich10 encountered an error on the sata interface wh ich caused the transfer to stop. 26 interface non-fatal error status (infs) ? r/wc. indicates that the ich10 encountered an error on the sata interfa ce but was able to continue operation. 25 reserved 24 overflow status (ofs) ? r/wc . indicates that the ich10 re ceived more bytes from a device than was specified in the prd table for the command. 23 incorrect port multiplier status (ipms) ? r/wc. indicates that the ich10 received a fis from a device whose port multiplier field did not match what was expected. note: port multiplier not supported by ich10. 22 phyrdy change status (prcs) ? ro. when set to one indicates the internal phyrdy signal changed state. this bi t reflects the state of pxserr .diag.n. unlike most of the other bits in the register, th is bit is ro and is only cl eared when pxserr.diag.n is cleared. note that the internal phyrdy signal also transitions when the po rt interface enters partial or slumber power mana gement states. partial and slumber must be disabled when surprise removal notification is desi red, otherwise the po wer management state transitions will appe ar as false insertio n and removal events. 21:8 reserved 7 device interlock status (dis) ? r/wc. when set, indicates that a platform interlock switch has been opened or cl osed, which may lead to a chan ge in the connection state of the device. this bit is only valid in systems that support an interlock switch (cap.sis [abar+00:bit 28] set). for systems that do not support an interl ock switch, this bit will always be 0. 6 port connect change status (pcs) ? ro. this bit refl ects the state of pxserr.diag.x. (abar+130h/1d0h/230h/2d0h, bit 26) unlike other bits in this register, this bit is only cleare d when pxserr.diag.x is cleared. 0 = no change in current connect status. 1 = change in current connect status. 5 descriptor pr ocessed (dps) ? r/wc. a prd with the i bit set has transferred all its data. http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 550 datasheet 14.4.3.6 pxie?port [5:0] interru pt enable register (d31:f2) address offset: port 0: abar + 114h attribute: r/w, ro port 1: abar + 194h port 2: abar + 214h port 3: abar + 294h port 4: abar + 314h port 5: abar + 394h default value: 00000000h size: 32 bits this register enables and disables the re porting of the corresponding interrupt to system software. when a bit is set (?1?) an d the corresponding interrupt condition is active, then an interrupt is generated. inte rrupt sources that are disabled (?0?) are still reflected in the status registers. 4 unknown fis interrupt (ufs) ? ro. when set to ?1? indicates that an unknown fis was received and has been copied into syst em memory. this bit is cleared to ?0? by software clearing the pxserr.diag.f bit to ?0?. note th at this bit does not directly reflect the pxserr.diag.f bit. pxserr.diag.f is set immediately when an unknown fis is detected, whereas this bit is set wh en the fis is posted to memory. software should wait to act on an unknown fis until this bit is set to ?1? or the two bits may become out of sync. 3 set device bits interrupt (sdbs) ? r/wc. a set device bits fis has been received with the i bit set and has been copied into system memory. 2 dma setup fis interrupt (dss) ? r/wc. a dma setup fis has been received with the i bit set and has been co pied into system memory. 1 pio setup fis interrupt (pss) ? r/wc . a pio setup fis has been received with the i bit set, it has been copied into system memory, and the data related to that fis has been transferred. 0 device to host register fis interrupt (dhrs) ? r/wc. a d2h register fis has been received with the i bit set, and has been copied into system memory. bit description bit description 31 cold presence detect enable (cpde) ? ro. cold presence detect is not supported. 30 task file error enable (tfee) ? r/w . when set, and ghc.ie and pxtfd.sts.err (due to a reception of the error register from a received fis) are set, the intel ? ich10 will generate an interrupt. 29 host bus fatal error enable (hbfe) ? r/w . when set, and ghc.ie and pxs.hbfs are set, the ich10 will generate an interrupt. 28 host bus data error enable (hbde) ? r/w . when set, and ghc.ie and pxs.hbds are set, the ich10 will generate an interrupt. 27 host bus data error enable (hbde) ? r/w. when set, ghc.ie is set, and pxis.hbds is set, the ich10 will generate an interrupt. 26 interface non-fatal error enable (infe) ? r/w. when set, ghc.ie is set, and pxis.infs is set, the ich10 will generate an interrupt. 25 reserved 24 overflow error enable (ofe) ? r/w . when set, and ghc.ie and pxs.ofs are set, the ich10 will generate an interrupt. http://www..net/ datasheet pdf - http://www..net/ datasheet 551 sata controller registers (d31:f2) 23 incorrect port multiplier enable (ipme) ? r/w. when set, and ghc.ie and pxis.ipms are set, the ich10 will generate an interrupt. note: should be written as 0. port mu ltiplier not supported by ich10. 22 phyrdy change interrupt enable (prce) ? r/w. when set, and ghc.ie is set, and pxis.prcs is set, the ich10 shall generate an interrupt. 21:8 reserved 7 device interlock enable (die) ? r/w. when set, and pxis.dis is set, the ich10 will generate an interrupt. for systems that do not support an interloc k switch, this bit shall be a read-only 0. 6 port change interrupt enable (pce) ? r/w . when set, and ghc.ie and pxs.pcs are set, the ich10 will generate an interrupt. 5 descriptor processed interrupt enable (dpe) ? r/w . when set, and ghc.ie and pxs.dps are set, the ich10 will generate an interrupt 4 unknown fis interrupt enable (ufie) ? r/w . when set, and ghc.ie is set and an unknown fis is received, the ich 10 will generate this interrupt. 3 set device bits fis interrupt enable (sdbe) ? r/w . when set, and ghc.ie and pxs.sdbs are set, the ich10 will generate an interrupt. 2 dma setup fis interrupt enable (dse) ? r/w . when set, and ghc.ie and pxs.dss are set, the ich10 will generate an interrupt. 1 pio setup fis interrupt enable (pse) ? r/w . when set, and ghc.ie and pxs.pss are set, the ich10 will generate an interrupt. 0 device to host register fis interrupt enable (dhre) ? r/w . when set, and ghc.ie and pxs.dhrs are set, the ich10 will generate an interrupt. bit description http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 552 datasheet 14.4.3.7 pxcmd?port [5:0] command register (d31:f2) address offset: port 0: abar + 118h attribute: r/w, ro, r/wo port 1: abar + 198h port 2: abar + 218h port 3: abar + 298h port 4: abar + 318h port 5: abar + 398h default value: 0000w00wh size: 32 bits where w = 00?0b (for?, see bit description) function level reset:no (bit 21, 19 and 18 only) bit description 31:28 interface communication control (icc) ? r/w . this is a four bit field which can be used to control reset and power states of the inte rface. writes to this field will cause actions on the interface, either as primitives or an oob sequence, and the resulting status of the interface will be reported in the pxssts register (address offset port 0:abar+124h, port 1: abar+1a4h, port 2: abar+224h, port 3: abar+2a4h, port 4: ab ar+224h, port 5: abar+2a4h). when system software writes a non-rese rved value other than no-op (0h), the ich10 will perform the action and upda te this field back to idle (0h). if software writes to this field to change the state to a state the link is already in (e.g. interface is in the ac tive state and a request is made to go to the active state), the ich10 will take no acti on and return this field to idle. note: when the alpe bit (bit 26) is set, then this register should not be set to 02h or 06h. 27 aggressive slumber / partial (asp) ? r/w . when set, and th e alpe bit (bit 26) is set, the ich10 shall aggressively en ter the slumber state when it clears the pxci register and the pxsact register is cleared. when cleared, and the alpe bit is set, the ich10 will aggressively enter th e partial state when it clears the pxci register and the pxsact regist er is cleared. if cap.salp is cleared to '0', software shall treat this bit as reserved. 26 aggressive link power ma nagement enable (alpe) ? r/w . when set, the ich10 will aggressively enter a lower link power state (partial or slumber) based upon the setting of the asp bit (bit 27). value definition fh?7h reserved 6h slumber: this will cause the intel ? ich10 to request a transition of the interface to the slumber state. the sata device may reject the request and the interface will remain in its current state 5h?3h reserved 2h partial: this will cause the ich1 0 to request a transition of the interface to the partial state. the sata device may reject the request and the interface will remain in its current state. 1h active: this will cause the ich10 to request a transition of the interface into the active 0h no-op / idle: when software read s this value, it indicates the ich10 is not in the process of changing the inte rface state or sending a device reset, and a new link command may be issued. http://www..net/ datasheet pdf - http://www..net/ datasheet 553 sata controller registers (d31:f2) 25 drive led on atapi enable (dlae) ? r/w . when set, the ich10 will drive the led pin active for atapi commands (pxc lb[chz.a] set) in addition to ata commands. when cleared, the ich10 will only drive the led pin active for ata commands. see section 5.16.9 for details on the activity led. 24 device is atapi (atapi) ? r/w. when set, the connected device is an atapi device. this bit is used by the ich10 to control whether or not to generate the desktop led when commands are active. see section 5.16.9 for details on the activity led. 23:22 reserved 21 external sata port (esp) ? r/wo. 0 = this port supports internal sata devices only. 1 = this port will be used with an extern al sata device and ho t plug is supported. when set, cap.sxs must also be set. this bit is not reset by function level reset. 20 reserved 19 interlock switch attached to port (isp) ? r/wo. when interlock switches are supported in the platform (cap.sis [abar+ 00h:bit 28] set), this indicates whether this particular port has an interlock switch attached. this bit can be used by system software to enable such features as aggressive power management, as disconnects can always be detected regard less of phy state with an interlock switch. when this bit is set, it is expected that hpcp (bit 18) in th is register is also set. the ich10 takes no action on the state of th is bit ? it is for system software only. for example, if this bit is cleared, and an interlock switch toggles, the ich10 still treats it as a proper interlock switch event. note that these bits are not reset on a controller reset. this bit is not reset by function level reset. 18 hot plug capable port (hpcp) ? r/wo. 0 = port is not capable of hot-plug. 1 = port is hot-plug capable. this indicates whether the pl atform exposes this port to a device which can be hot- plugged. sata by definition is hot-pluggable, but not all platforms ar e constructed to allow the device to be removed (it may be screwed into the chassis, for example). this bit can be used by system software to indicate a feature such as ?eject device? to the end-user. the ich10 takes no action on the state of this bit - it is for system software only. for example, if this bit is cleared, and a hot-plug event occurs, the ich10 still treats it as a proper hot-plug event. note that these bits are not reset on a controller reset. this bit is not reset by function level reset. 17 port multiplier attached (pma) ? ro / r/w. when this bit is set, a port multiplier is attached to the ich10 for this port. when cleared, a port multiplier is not attached to this port. this bit is ro 0 when cap.pms (offset abar+00h:bit 17) = 0 and r/w when cap.pms = 1. this bit may only be set when px.cmd.st is cleared. 16 port multiplier fis based switching enable (pmfse) ? ro. the ich10 does not support fis-based switching. note: fis port multiplier not supported by ich10. 15 controller running (cr) ? ro. when this bit is set, th e dma engines for a port are running. see section 5.2.2 of the serial ata ahci specification for details on when this bit is set an d cleared by the ich10. bit description http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 554 datasheet 14 fis receive running (fr) ? ro. when set, the fis receive dma engine for the port is running. see section 12.2.2 of the serial ata ahci specification for details on when this bit is set and cleared by the ich10. 13 interlock switch state (iss) ? ro. for systems that su pport interlock switches (via cap.sis [abar+00h:bit 28]), if an interlock switch exists on this port (via isp in this register), this bit indicates the current state of the interlock switch. a 0 indicates the switch is closed, and a 1 indicates the switch is opened. for systems that do not support interlock sw itches, or if an inte rlock switch is not attached to this port , this bit reports 0. 12:8 current command slot (ccs) ? ro . indicates the current command slot the ich10 is processing. this field is valid when the st bit is set in this register, and is constantly updated by the ich10. this fi eld can be updated as soon as the ich10 recognizes an active command slot, or at some point soon af ter when it begins processing the command. this field is used by soft ware to determine the current command issue location of the ich10. in queued mode, software shall not use this field, as its value does not represent the current command being executed. software shall only use pxci and pxsact when running queued commands. 7:5 reserved 4 fis receive enable (fre) ? r/w. when set, the ich10 may post received fises into the fis receive area pointed to by pxfb (abar+108h/188h/208h/288h) and pxfbu (abar+10ch/18ch/20ch/28ch). when cleared, received fises are not accepted by the ich10, except for the first d2h (device-to-host) register fis after the initialization sequence. system software must not set this bit unt il pxfb (pxfbu) have been programmed with a valid pointer to the fis receive ar ea, and if software wishes to move the base, this bit must first be cl eared, and software must wait for the fr bit (bit 14) in this register to be cleared. 3 command list override (clo) ? r/w. setting this bit to '1' causes pxtfd.sts.bsy and pxtfd.sts.drq to be cl eared to '0'. this allows a software reset to be transmitted to the device re gardless of whether the bsy and drq bits are still set in the pxtfd.sts register. the controller sets this bit to '0' when pxtfd.sts.bsy and pxtfd.sts.drq have been cleared to '0'. a write to this register with a value of '0' shall have no effect. this bit shall only be set to '1' immediatel y prior to setting the pxcmd.st bit to '1' from a previous value of '0'. setting this bit to '1' at any other time is not supported and will result in indeterminate behavior. soft ware must wait for clo to be cleared to '0' before setting pxcmd.st to '1'. bit description http://www..net/ datasheet pdf - http://www..net/ datasheet 555 sata controller registers (d31:f2) 14.4.3.8 pxtfd?port [5:0] task file data register (d31:f2) address offset: port 0: abar + 120h attribute: ro port 1: abar + 1a0h port 2: abar + 220h port 3: abar + 2a0h port 4: abar + 320h port 5: abar + 3a0h default value: 0000007fh size: 32 bits this is a 32-bit register that copies specif ic fields of the task file when fises are received. the fises that contain this information are: d2h register fis pio setup fis set device bits fis 2 power on device (pod) ? ro . cold presence detect no t supported. defaults to 1. 1 spin-up device (sud) ? r/w / ro this bit is r/w and defaults to 0 for sy stems that support st aggered spin-up (r/w when cap.sss (abar+00h:bit 27) is 1). bit is ro 1 for systems that do not support staggered spin-up (when cap.sss is 0). 0 = no action. 1 = on an edge detect from 0 to 1, the ich10 starts a comreset initialization sequence to the device. clearing this bit to '0' does not cause an y oob signal to be se nt on the interface. when this bit is cleared to '0' and pxsctl .det=0h, the controll er will enter listen mode. 0 start (st) ? r/w . when set, the ich10 may process the command list. when cleared, the ich10 may not process the command list. whenever this bit is changed from a 0 to a 1, the ich10 starts processing the command list at entry 0. whenever this bit is changed from a 1 to a 0, the pxci register is cleared by the ich10 upon the ich10 putting the controller into an idle state. refer to section 12.2.1 of the serial ata ahci specification for important restrictions on when st can be set to 1. bit description bit description 31:16 reserved 15:8 error (err) ? ro . contains the latest copy of the task file error register. 7:0 status (sts) ? ro . contains the latest copy of the task file status register. fields of note in this register that affect ahci. bit field definition 7 bsy indicates the interface is busy 6:4 n/a not applicable 3 drq indicates a data transfer is requested 2:1 n/a not applicable 0 err indicates an error during the transfer http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 556 datasheet 14.4.3.9 pxsig?port [5:0] signature register (d31:f2) address offset: port 0: abar + 124h attribute: ro port 1: abar + 1a4h port 2: abar + 224h port 3: abar + 2a4h port 4: abar + 324h port 5: abar + 3a4h default value: ffffffffh size: 32 bits this is a 32-bit register which contains the initial signature of an attached device when the first d2h register fis is received from th at device. it is updated once after a reset sequence. bit description 31:0 signature (sig) ? ro . contains the signature received from a device on the first d2h register fis. the bit order is as follows: bit field 31:24 lba high register 23:16 lba mid register 15:8 lba low register 7:0 sector count register http://www..net/ datasheet pdf - http://www..net/ datasheet 557 sata controller registers (d31:f2) 14.4.3.10 pxssts?port [5:0] serial ata status register (d31:f2) address offset: port 0: abar + 128h attribute: ro port 1: abar + 1a8h port 2: abar + 228h port 3: abar + 2a8h port 4: abar + 328h port 5: abar + 3a8h default value: 00000000h size: 32 bits this is a 32-bit register that conveys the current state of the interface and host. the ich10 updates it continuously and asyn chronously. when the ich10 transmits a comreset to the device, this register is updated to its reset values. bit description 31:12 reserved 11:8 interface power management (ipm) ? ro . indicates the current interface state: all other values reserved. 7:4 current interface speed (spd) ? ro. indicates the negotiated interface communication speed. all other values reserved. ich10 supports generation 1 communication rates (1.5 gb/s) and gen 2 rates (3.0 gb/ s). 3:0 device detection (det) ? ro . indicates the interface de vice detection and phy state: all other values reserved. value description 0h device not present or communication not established 1h interface in active state 2h interface in partial power management state 6h interface in slumber power management state value description 0h device not present or communication not established 1h generation 1 communication rate negotiated 2h generation 2 communication rate negotiated value description 0h no device de tected and phy communication not established 1h device presence detected but phy communication not established 3h device presence detected and phy communication established 4h phy in offline mode as a result of the interface being disabled or running in a bist loopback mode http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 558 datasheet 14.4.3.11 pxsctl ? port [5:0] serial ata control register (d31:f2) address offset: port 0: abar + 12ch attribute: r/w, ro port 1: abar + 1ach port 2: abar + 22ch port 3: abar + 2ach port 4: abar + 32ch port 5: abar + 3ach default value: 00000004h size: 32 bits this is a 32-bit read-write register by which software controls sata capabilities. writes to the scontrol register result in an action being taken by the ic h10 or the interface. reads from the register return the last value written to it. bit description 31:20 reserved 19:16 port multiplier port (pmp) ? r/w. this field is not used by ahci 15:12 select power management (spm) ? r/w. this field is not used by ahci 11:8 interface power management transitions allowed (ipm) ? r/w . indicates which power states the ich10 is allowed to transition to: all other values reserved 7:4 speed allowed (spd) ? r/w. indicates the highest al lowable speed of the interface. this speed is limited by the ca p.iss (abar+00h:bit 23:20) field. ich10 supports generation 1 communication rates (1.5 gb/s) and gen 2 rates (3.0 gb/s). value description 0h no interface restrictions 1h transitions to the partial state disabled 2h transitions to the slumber state disabled 3h transitions to both partial and slumber states disabled value description 0h no speed negotiation restrictions 1h limit speed negotiation to generation 1 communication rate 2h limit speed negotiation to generation 2 communication rate http://www..net/ datasheet pdf - http://www..net/ datasheet 559 sata controller registers (d31:f2) 14.4.3.12 pxserr?port [5:0] seri al ata error register (d31:f2) address offset: port 0: abar + 130h attribute: r/wc port 1: abar + 1b0h port 2: abar + 230h port 3: abar + 2b0h port 4: abar + 330h port 5: abar + 3b0h default value: 00000000h size: 32 bits bits 26:16 of this register contains diagnostic error information for use by diagnostic software in validating correct operation or isolating failure modes. bits 11:0 contain error information used by host software in determining the appropriate response to the error condition. if one or more of bits 11:8 of this register are set, the controller will stop the current transfer. 3:0 device detection initialization (det) ? r/w. controls the ich10? s device detection and interface initialization. all other values reserved. when this field is written to a 1h, the ich10 initiates comreset and starts the initialization process. when the initialization is complete, this field shall remain 1h until set to another value by software. this field may only be changed to 1h or 4h when pxcmd.st is 0. changing this field while the ich10 is running re sults in undefined behavior. note: it is permissible to implement any of the serial ata defined behaviors for transmission of comreset when det=1h. bit description value description 0h no device detection or initialization action requested 1h perform interface communication initialization sequence to establish communication. this is fu nctionally equivalent to a hard reset and results in the interface being reset and communications re-initialized 4h disable the serial ata interface and put phy in offline mode bit description 31:27 reserved 26 exchanged (x) ? r/wc. when set to one this bit indicates that a change in device presence has been detected since the last time this bit was cleared. this bit shall always be set to 1 anytime a cominit signal is received. th is bit is reflected in the p0is.pcs bit. 25 unrecognized fis type (f) ? r/wc. indicates that one or more fiss were received by the transport layer with good crc, but had a type field that was not recognized. 24 transport state transition error (t) ? r/wc. indicates that an error has occurred in the transition from one state to another within the transpor t layer since the last time this bit was cleared. 23 transport state transition error (t) ? r/wc. indicates that an error has occurred in the transition from one state to another within the transpor t layer since the last time this bit was cleared. http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 560 datasheet 22 handshake (h) ? r/wc. indicates that one or more r_err handshake response was received in response to fram e transmission. such errors may be the result of a crc error detected by the recipien t, a disparity or 8b/10b deco ding error, or other error condition leading to a negative handshake on a transmitted frame. 21 crc error (c) ? r/wc. indicates that one or more crc errors occurred with the link layer. 20 disparity error (d) ? r/wc. this field is not used by ahci. 19 10b to 8b decode error (b) ? r/wc. indicates that one or more 10b to 8b decoding errors occurred. 18 comm wake (w) ? r/wc. indicates that a comm wake signal was detected by the phy. 17 phy internal error (i) ? r/wc. indicates that the phy detected some internal error. 16 phyrdy change (n) ? r/wc. when set to 1 this bit indicates that the internal phyrdy signal changed state since the last time this bit was cleared. in the ich10, this bit will be set when phyrdy changes fro m a 0 -> 1 or a 1 -> 0. the state of this bit is then reflected in the pxis.prcs interrupt status bit and an interrupt will be generated if enabled. software cl ears this bit by writing a 1 to it. 15:12 reserved 11 internal error (e) ? r/wc. the sata controller failed due to a master or target abort when attempting to access system memory. 10 protocol error (p) ? r/wc. a violation of the serial ata protocol was detected. note: the ich10 does not set this bit for all protocol violations th at may occur on the sata link. 9 persistent communication or data integrity error (c) ? r/wc. a communication error that was not recovered occurred that is expected to be pe rsistent. persistent communications errors may arise from faulty interconne ct with the device, from a device that has been removed or has failed, or a number of other causes. 8 transient data integrity error (t) ? r/wc. a data integrity error occurred that was not recovered by the interface. 7:2 reserved. 1 recovered communications error (m) ? r/wc. communications between the device and host was temporarily lost but was re-established. this can arise from a device temporarily be ing removed, from a temporary loss of phy synchronization, or from other causes and may be derived fro m the phynrdy signal between the phy and link layers. 0 recovered data integrity error (i) ? r/wc. a data integrity error occurred that was recovered by the interface through a re try operation or other recovery action. bit description http://www..net/ datasheet pdf - http://www..net/ datasheet 561 sata controller registers (d31:f2) 14.4.3.13 pxsact?port [5:0] serial ata active (d31:f2) address offset: port 0: abar + 134h attribute: r/w port 1: abar + 1b4h port 2: abar + 234h port 3: abar + 2b4h port 4: abar + 334h port 5: abar + 3b4h default value: 00000000h size: 32 bits 14.4.3.14 pxci?port [5:0] command issue register (d31:f2) address offset: port 0: abar + 138h attribute: r/w port 1: abar + 1b8h port 2: abar + 238h port 3: abar + 2b8h port 4: abar + 338h port 5: abar + 3b8h default value: 00000000h size: 32 bits bit description 31:0 device status (ds) ? r/w. system software sets this bi t for sata queuing operations prior to setting the pxci.ci bit in the same co mmand slot entry. this field is cleared via the set device bits fis. this field is also cleared when pxcmd. st (abar+118h/198h/218h/298h:bit 0) is cleared by software, and as a re sult of a comreset or srst. bit description 31:0 commands issued (ci) ? r/w. this field is set by software to indicate to the ich10 that a command has been built-in system me mory for a command slot and may be sent to the device. when the ich10 receives a fis which clears the bsy and drq bits for the command, it clears the corresponding bit in th is register for that command slot. bits in this field shall only be set to '1' by software when pxcmd.st is set to '1'. this field is also cleared when pxcmd. st (abar+118h/198h/218h/298h:bit 0) is cleared by software. http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f2) 562 datasheet http://www..net/ datasheet pdf - http://www..net/ datasheet 563 sata controller registers (d31:f5) 15 sata controller registers (d31:f5) 15.1 pci configuration registers (sata?d31:f5) note: address locations that are not shown should be treated as reserved. all of the sata registers are in the core well. none of the registers can be locked. table 15-1. sata controller pci register address map (sata?d31:f5) (sheet 1 of 2) offset mnemonic register name default type 00h?01h vid vendor identification 8086h ro 02h?03h did device identification see register description ro 04h?05h pcicmd pci command 0000h r/w, ro 06h?07h pcists pci status 02b0h r/wc, ro 08h rid revision identification see register description ro 09h pi programming interface see register description see register description 0ah scc sub class code see register description see register description 0bh bcc base class code 01h ro 0dh pmlt primary master latency timer 00h ro 10h?13h pcmd_bar primary command block base address 00000001h r/w, ro 14h?17h pcnl_bar primary control block base address 00000001h r/w, ro 18h?1bh scmd_bar secondary command block base address 00000001h r/w, ro 1ch?1fh scnl_bar secondary control block base address 00000001h r/w, ro 20h?23h bar legacy bus master base address 00000001h r/w, ro 24h?27h sidpba serial ata index / data pair base address 00000000h see register description 2ch?2dh svid subsystem vendor identification 0000h r/wo 2eh?2fh sid subsystem identification 0000h r/wo 34h cap capabilities pointer 80h ro 3ch int_ln interrupt line 00h r/w 3dh int_pn interrupt pin see register description ro http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f5) 564 datasheet note: the ich10 sata controller is not arbitrated as a pci device, therefore it does not need a master latency timer. 15.1.1 vid?vendor iden tification regist er (sata?d31:f5) offset address: 00h ? 01h attribute: ro default value: 8086h size: 16 bit lockable: no power well: core 40h-41h ide_tim primary ide timing register 0000h r/w 42h-43h ide_tim secondary ide timing registers 0000h r/w 70h?71h pid pci power management capability id see register description ro 72h?73h pc pci power management capabilities 4003h ro 74h?75h pmcs pci power management control and status 0008h r/w, ro, r/wc 80h?81h (consumer only) msici message signaled in terrupt capability id 7005h ro 82h?83h (consumer only) msimc message signaled interrupt message control 0000h ro, r/w 84h?87h (consumer only) msima message signaled interrupt message address 00000000h ro, r/w 88h?89h (consumer only) msimd message signaled interrupt message data 0000h r/w 90h map address map 00h r/w 92h?93h pcs port control and status 0000h r/w, ro, r/wc a8h?abh scap0 sata capability register 0 0010b012h ro ach?afh scap1 sata capability register 1 00000048h ro b0h?b1h flrcid flr capability id 0009h ro b2h?b3h flrclv flr capability length and value 2006h ro b4h?b5h flrctrl flr control 0000h r/w, ro c0h atc apm trapping control 00h r/w c4h ats atm trapping status 00h r/wc table 15-1. sata controller pci register address map (sata?d31:f5) (sheet 2 of 2) offset mnemonic register name default type bit description 15:0 vendor id ? ro. this is a 16-bit value as signed to intel. intel vid = 8086h http://www..net/ datasheet pdf - http://www..net/ datasheet 565 sata controller registers (d31:f5) 15.1.2 did?device identificati on register (sata?d31:f5) offset address: 02h ? 03h attribute: ro default value: see bit description size: 16 bit lockable: no power well: core 15.1.3 pcicmd?pci command register (sata?d31:f5) address offset: 04h ? 05h attribute: ro, r/w default value: 0000h size: 16 bits bit description 15:0 device id ? ro. this is a 16-bit value assigned to the intel ? ich10 sata controller. note: the value of this field will change dependent upon the value of the map register. see section 15.1.29 bit description 15:11 reserved 10 interrupt disable ? r/w. this disables pin-based intx# interrupts. this bit has no effect on msi operation. 0 = internal intx# messages are generated if there is an interrupt and msi is not enabled. 1 = internal intx# messages will not be generated. 9 fast back to back enable (fbe) ? ro. reserved as 0. 8 serr# enable (serr_en) ? ro. reserved as 0. 7 wait cycle control (wcc) ? ro. reserved as 0. 6 parity error response (per) ? r/w. 0 = disabled. sata controller will not gene rate perr# when a data parity error is detected. 1 = enabled. sata controller will generate perr# when a data pari ty error is detected. 5 vga palette snoop (vps) ? ro. reserved as 0. 4 postable memory write enable (pmwe) ? ro. reserved as 0. 3 special cycle en able (sce) ? ro. reserved as 0. 2 bus master enable (bme) ? r/w. this bit controls the ich10?s ability to act as a pci master for ide bus master transfers. this bit does not impact the generation of completions for split transaction commands. 1 memory space enable (mse) ? ro. this controller does not support ahci, therefore no memory space is required. 0 i/o space enable (iose) ? r/w. this bit controls access to the i/o space registers. 0 = disables access to the legacy or native ide ports (both primary and secondary) as well as the bus mast er i/o registers. 1 = enable. note that the base address register for the bus master registers should be programmed before this bit is set. http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f5) 566 datasheet 15.1.4 pcists ? pci status register (sata?d31:f5) address offset: 06h ? 07h attribute: r/wc, ro default value: 02b0h size: 16 bits note: for the writable bits, software must write a 1 to clear bits that are set. writing a 0 to the bit has no effect. 15.1.5 rid?revision identificati on register (sata?d31:f5) offset address: 08h attribute: ro default value: see bit description size: 8 bits bit description 15 detected parity error (dpe) ? r/wc. 0 = no parity error detected by sata controller. 1 = sata controller detects a parity error on its interface. 14 signaled system error (sse) ? ro. reserved as 0. 13 received master abort (rma) ? r/wc. 0 = master abort not generated. 1 = sata controller, as a master , generated a master abort. 12 reserved 11 signaled target abort (sta) ? ro. reserved as 0. 10:9 devsel# timing status (dev_sts) ? ro. 01 = hardwired; controls the devi ce select time for the sata controller?s pci interface. 8 data parity error detected (dped) ? r/wc. for ich10, this bit can only be set on read completions received from sibu s where there is a parity error. 1 = sata controller, as a master, either detect s a parity error or sees the parity error line asserted, and the parity error response bit (bit 6 of the command register) is set. 7 fast back to back capable (fb2bc) ? ro. reserved as 1. 6 user definable features (udf) ? ro. reserved as 0. 5 66mhz capable (66mhz_cap) ? ro. reserved as 1. 4 capabilities list (cap_list) ? ro. this bit indicates the presence of a capabilities list. the minimum requirement for the capabili ties list must be pci power management for the sata controller. 3 interrupt status (ints) ? ro. reflects the state of intx# messages, irq14 or irq15. 0 = interrupt is cleared (ind ependent of the state of in terrupt disabl e bit in the command register [offset 04h]). 1 = interrupt is to be asserted 2:0 reserved bit description 7:0 revision id ? ro. refer to the intel ? i/o controller hub (ich10) family specification update for the value of the revision id register http://www..net/ datasheet pdf - http://www..net/ datasheet 567 sata controller registers (d31:f5) 15.1.6 pi?programmin g interface register (sata?d31:f5) address offset: 09h attribute: ro default value: 85h size: 8 bits when scc = 01h 15.1.7 scc?sub class code register (sata?d31:f5) address offset: 0ah attribute: ro default value: 01h size: 8 bits 15.1.8 bcc?base clas s code register (sata?d31:f5) address offset: 0bh attribute: ro default value: 01h size: 8 bits bit description 7 this read-only bit is a 1 to indicate th at the ich10 supports bus master operation 6:4 reserved. 3 secondary mode native capable (snc) ? ro. indicates whether or not the secondary channel has a fixed mode of operation. 0 = indicates the mode is fixed and is dete rmined by the (read-only) value of bit 2. this bit will always return ?0?. 2 secondary mode nati ve enable (sne) ? ro. determines the mode th at the secondary channel is operating in. 1 = secondary controller operating in native pci mode. this bit will always return ?1?. 1 primary mode native capable (pnc) ? ro. indicates whether or not the primary channel has a fixed mode of operation. 0 = indicates the mode is fixed and is dete rmined by the (read-only) value of bit 0. this bit will always return ?0?. 0 primary mode native enable (pne) ? ro. determines the mode that the primary channel is operating in. 1 = primary controller operating in native pci mode. this bit will always return ?1?. bit description 7:0 sub class code (scc) ? ro. the value of this field determines whethe r the controller supports legacy ide mode. bit description 7:0 base class code (bcc) ? ro. 01h = mass storage device http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f5) 568 datasheet 15.1.9 pmlt?primary master latency timer register (sata?d31:f5) address offset: 0dh attribute: ro default value: 00h size: 8 bits 15.1.10 pcmd_bar?primary co mmand block base address register (sata?d31:f5) address offset: 10h ? 13h attribute: r/w, ro default value: 00000001h size: 32 bits . note: this 8-byte i/o space is used in native mo de for the primary cont roller?s command block. 15.1.11 pcnl_bar?primary contro l block base address register (sata?d31:f5) address offset: 14h ? 17h attribute: r/w, ro default value: 00000001h size: 32 bits . note: this 4-byte i/o space is used in native mo de for the primary cont roller?s command block. bit description 7:0 master latency timer count (mltc) ? ro. 00h = hardwired. the sata controller is im plemented internally, and is not arbitrated as a pci device, so it does no t need a master latency timer. bit description 31:16 reserved 15:3 base address ? r/w. this field provides the base address of the i/o space (8 consecutive i/o locations). 2:1 reserved 0 resource type indicator (rte) ? ro. hardwired to 1 to indicate a request for i/o space. bit description 31:16 reserved 15:2 base address ? r/w. this field provides the base address of the i/o space (4 consecutive i/o locations). 1 reserved 0 resource type indicator (rte) ? ro. hardwired to 1 to indicate a request for i/o space. http://www..net/ datasheet pdf - http://www..net/ datasheet 569 sata controller registers (d31:f5) 15.1.12 scmd_bar?secondary co mmand block base address register (ide d31:f1) address offset: 18h ? 1bh attribute: r/w, ro default value: 00000001h size: 32 bits note: this 8-byte i/o space is used in native mode for the secondary controller?s command block. 15.1.13 scnl_bar?secondary co ntrol block base address register (ide d31:f1) address offset: 1ch ? 1fh attribute: r/w, ro default value: 00000001h size: 32 bits note: this 4-byte i/o space is used in native mode for the secondary controller?s command block. bit description 31:16 reserved 15:3 base address ? r/w. this field provides the base address of the i/o space (8 consecutive i/o locations). 2:1 reserved 0 resource type indicator (rte) ? ro. hardwired to 1 to indicate a request for i/o space. bit description 31:16 reserved 15:2 base address ? r/w. this field provides the base address of the i/o space (4 consecutive i/o locations). 1 reserved 0 resource type indicator (rte) ? ro. hardwired to 1 to indicate a request for i/o space. http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f5) 570 datasheet 15.1.14 bar ? legacy bus master base address register (sata?d31:f5) address offset: 20h ? 23h attribute: r/w, ro default value: 00000001h size: 32 bits the bus master ide interface function uses base address register 5 to request a 16- byte io space to provide a software interf ace to the bus master functions. only 12 bytes are actually used (6 bytes for primary, 6 bytes for secondary). only bits [15:4] are used to decode the address. 15.1.15 sidpba ? sata index/data pair base a ddress register (sata?d31:f5) address offset: 24h ? 27h attribute: r/w, ro default value: 00000000h size: 32 bits when scc is 01h when the programming interface is ide, the register represents an i/o bar allocating 16b of i/o space for the i/o mapped registers defined in section 15.3 . note that although 16b of locations are allocated, some maybe reserved. bit description 31:16 reserved 15:5 base address ? r/w. this field provides the ba se address of the i/o space (16 consecutive i/o locations). 4 base address 4 (ba4) ? r/w. when scc is 01h, this bit will be r/w re sulting in requesting 16b of i/o space. 3:1 reserved 0 resource type indicator (rte) ? ro. hardwired to 1 to indicate a request for i/o space. bit description 31:16 reserved 15:4 base address (ba) ? r/w. base address of register i/o space 3:1 reserved 0 resource type indicator (rte) ? ro. hardwired to 1 to indicate a request for i/o space. http://www..net/ datasheet pdf - http://www..net/ datasheet 571 sata controller registers (d31:f5) 15.1.16 svid?subsystem vendor identification register (sata?d31:f5) address offset: 2ch ? 2dh attribute: r/wo default value: 0000h size: 16 bits lockable: no power well: core function level reset: no 15.1.17 sid?subsystem identification register (sata?d31:f5) address offset: 2eh ? 2fh attribute: r/wo default value: 0000h size: 16 bits lockable: no power well: core 15.1.18 cap?capabilities poin ter register (sata?d31:f5) address offset: 34h attribute: ro default value: 70h size: 8 bits 15.1.19 int_ln?interrupt line register (sata?d31:f5) address offset: 3ch attribute: r/w default value: 00h size: 8 bits function level reset: no 15.1.20 int_pn?interrupt pi n register (sata?d31:f5) address offset: 3dh attribute: ro default value: see register description size: 8 bits bit description 15:0 subsystem vendor id (svid) ? r/wo. value is written by bios. no hardware action taken on this value. bit description 15:0 subsystem id (sid) ? r/wo. value is written by bios. no hardware action taken on this value. bit description 7:0 capabilities pointer (cap_ptr) ? ro. indicates that the first capability pointer offset is 70h if the sub cl ass code (scc) (dev 31:f2:0ah ) is configure as ide mode (value of 01). bit description 7:0 interrupt line ? r/w. this field is used to communicate to software the interrupt line that the interrupt pin is connected to. these bits are not reset by flr. bit description 7:0 interrupt pin ? ro. this reflects the value of d31ip.sip1 (chipset config registers:offset 3100h:bits 11:8). http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f5) 572 datasheet 15.1.21 ide_tim ? ide timing register (sata?d31:f5) address offset: primary: 40h?41h attribute: r/w secondary: 42h?43h default value: 0000h size: 16 bits 15.1.22 pid?pci power management capability identification register (sata?d31:f5) address offset: 70h ? 71h attribute: ro default value: b001h size: 16 bits 15.1.23 pc?pci power manageme nt capabilities register (sata?d31:f5) address offset: 72h ? 73h attribute: ro default value: 4003h size: 16 bits f bit description 15 ide decode enable (ide) ? r/w. individually enable /disable the primary or secondary decode. 0 = disable. 1 = enables the intel ? ich10 to decode the associated command blocks (1f0?1f7h for primary, 170?177h for secondary) and control block (3f6h for primary and 376h for secondary). this bit effects the ide decode ranges fo r both legacy and native-mode decoding. note: this bit affects sata operation in both combined and non-combined ata modes. see section 5.16 for more on ata modes of operation. 14:0 reserved bits description 15:8 next capability (next) ? ro. when scc is 01h, this fi eld will be b0h indicating the next item is flr capability pointer in the list. 7:0 capability id (cid) ? ro. indicates that this poin ter is a pci power management. bits description 15:11 pme support (pme_sup) ? ro. by default with scc = 01h, the default value of 00000 indicates no pme support in ide mode. 10 d2 support (d2_sup) ? ro. hardwired to 0. the d2 state is not supported 9 d1 support (d1_sup) ? ro. hardwired to 0. the d1 state is not supported 8:6 auxiliary current (aux_cur) ? ro. pme# from d3 cold state is not supported, therefore this field is 000b. 5 device specific initialization (dsi) ? ro. ha rdwired to 0 to indicate that no device- specific initialization is required. 4 reserved 3 pme clock (pme_clk) ? ro. hardwired to 0 to in dicate that pci clock is not required to generate pme#. 2:0 version (ver) ? ro. hardwired to 011 to indicates support for revision 1.2 of the pci power management specification. http://www..net/ datasheet pdf - http://www..net/ datasheet 573 sata controller registers (d31:f5) 15.1.24 pmcs?pci power mana gement control and status register (sata?d31:f5) address offset: 74h ? 75h attribute: ro, r/w, r/wc default value: 0008h size: 16 bits function level reset: no (bits 8 and 15 only) 15.1.25 mid?message signal interru pt identifier (sata?d31:f5) (consumer only) address offset: 80h-81h attribute: ro default value: 7005h size: 16 bits bits description 15 pme status (pmes) ? r/wc. bit is set when a pme event is to be requested, and if this bit and pmee is set, a pme# will be generated from the sata controller. note: when scc=01h this bit will be ro ?0?. software is advised to clear pmee together with pmes prior to changing scc through map.sms. this bit is not reset by function level reset. 14:9 reserved 8 pme enable (pmee) ? r/w. when scc is not 01h, th is bit r/w. when set, the sata controller generates pme# form d3 hot on a wake event. note: when scc=01h this bit will be ro ?0?. software is advised to clear pmee together with pmes prior to changing scc through map.sms. this bit is not reset by function level reset. 7:4 reserved 3 no soft reset (nsfrst) ? ro. these bits are used to indicate whether devices transitioning from d3 hot state to d0 state will perform an internal reset. 0 = device transitioning from d3 hot state to d0 state perfo rm an internal reset. 1 = device transitioning from d3 hot state to d0 state do not perform an internal reset. configuration content is preserved. upon transition from the d3 hot state to d0 state initialized state, no addition al operating system interventi on is required to preserve configuration context beyond writing to the powerstate bits. regardless of this bit, the controller transition from d3 hot state to d0 state by a system or bus segment reset will return to the state d0 uninitialized with only pme context preserved if pme is supported and enabled. 2reserved 1:0 power state (ps) ? r/w. these bits are used both to determine the current power state of the sata controller and to set a new power state. 00 = d0 state 11 = d3 hot state when in the d3 hot state, the controller?s configurat ion space is available, but the i/o and memory spaces are not. addi tionally, interrupts are blocked. bits description 15:8 next pointer (next) ? ro. indicates the next item in the list is the pci power management pointer. 7:0 capability id (cid) ? ro. capability id indicate s message signal interrupt. http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f5) 574 datasheet 15.1.26 mc?message signal inte rrupt message control (sata? d31:f5) (consumer only) address offset: 82h-83h attribute: r/w, ro default value: 0000h size: 16 bits 15.1.27 ma?message signal inte rrupt message address (sata? d31:f5) (consumer only) address offset: 84h attribute: r/w, ro default value: 00000000h size: 32 bits 15.1.28 md?message signal in terrupt message data (sata? d31:f5) (consumer only) address offset: 88h attribute: r/w default value: 0000h size: 16 bits bits description 15:8 reserved. 7 64 bit address capable (c64) ? ro. capable of generati ng a 32-bit message only. 6:4 multiple message enable (mme) ? ro. this controller su pports a single interrupt message. this bit is ro ?0?. 3:1 multiple message capable (mmc) ? ro. system software reads this field to determine the number of reques ted vectors. this controller supports a single interrupt message, this field is ro ?0?. 0 msi enable (msie) ? r/w. if set, msi is enabled and traditional interrupt pins are not used to generate interrupts. note: cmd.id bit does not effect msi. softwa re must clear this bit to 0 to disable msi before changing the number of messages alloca ted in the mmc field. software must also make sure this bit is cleared to ?0? when op erating in legacy ide mode. this bit is r/w when scc is not 01h and is ro ?0? when scc is 01h. bits description 31:2 address (addr) ? r/w. lower 32 bits of the system specified message address, always dword aligned. 1:0 reserved. bits description 15:0 data (data) ? r/w. this 16-bit field is programm ed by system software if msi is enabled. its content is driven onto the lowe r word of the data bu s of the msi memory write transaction. note: when mc.mme field is set to a value other than ?000?, some bits of the msi memory write transaction will be driven based on the source of the interrupt rather than from md[2:0]. http://www..net/ datasheet pdf - http://www..net/ datasheet 575 sata controller registers (d31:f5) 15.1.29 map?address map re gister (sata?d31:f5)16 address offset: 90h attribute: r/w, r/wo, ro default value: 00h size: bits function level reset: no (bits 9:8 only) bits description 15:10 reserved. 9:8 reserved 7:6 sata mode select (sms) ? r/w. software programs these bits to control the mode in which the sata controller should operate. 00b = ide mode all other combinations are reserved. 5:2 reserved. 1:0 map value (mv) ? reserved. http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f5) 576 datasheet 15.1.30 pcs?port control and status register (sata?d31:f5) address offset: 92h ? 93h attribute: r/w, ro default value: 0000h size: 16 bits function level reset: no by default, the sata ports are set to the di sabled state (bits [5:0] = ?0?). when enabled by software, the ports can transition between the on, partial, and slumber states and can detect devices. when disabled, the port is in the ?off? state and cannot detect any devices. if an ahci-aware or raid enabled operating system is being booted then system bios shall insure that all supported sata ports are enabled prior to passing control to the os. once the ahci aware os is booted it becomes the enabling/disabling policy owner for the individual sata ports. this is acco mplished by manipulating a port?s pxsctl and pxcmd fields. because an ahci or raid awar e os will typically not have knowledge of the pxe bits and because the pxe bits act as master on/off switches for the ports, pre- boot software must insure that these bits are set to 1 prior to booting the os, regardless as to whether or not a device is currently on the port. bits description 15:10 reserved 9 port 5 present (p5p) ? ro. the status of this bit may change at any ti me. this bit is cleared when the port is disabled via p1e. this bit is not cleared upon surprise removal of a device. 0 = no device detected. 1 = the presence of a device on port 1 has been detected. 8 port 4 present (p4p) ? ro. the status of this bit may change at any ti me. this bit is cleared when the port is disabled via p0e. this bit is not cleared upon surprise removal of a device. 0 = no device detected. 1 = the presence of a device on port 0 has been detected. 7:2 reserved 1 port 5 enabled (p5e) ? r/w. 0 = disabled. the port is in the ?off? state and cannot detect any devices. 1 = enabled. the port can transition between the on, partial, and slumber states and can detect devices. this bit is read-only ?0? when map.spd[1]= 1. 0 port 4 enabled (p4e) ? r/w. 0 = disabled. the port is in the ?off? state and cannot detect any devices. 1 = enabled. the port can transition between the on, partial, and slumber states and can detect devices. this bit is read-only ?0? when map.spd[0]= 1. http://www..net/ datasheet pdf - http://www..net/ datasheet 577 sata controller registers (d31:f5) 15.1.31 satacr0? sata capabili ty register 0 (sata?d31:f5) address offset: a8h-abh attribute: ro, rwo default value: 0010b012h size: 32 bits function level reset: no (bits 15:8 only) note: when scc is 01h this re gister is read-only 0. . 15.1.32 satacr1? sata capabili ty register 1 (sata?d31:f5) address offset: ach-afh attribute: ro default value: 00000048h size: 32 bits when scc is 01h this re gister is read-only 0. . 15.1.33 flrcid? flr capability id (sata?d31:f5) address offset: b0h-b1h attribute: ro default value: 0009h size: 16 bits . bit description 31:24 reserved. 23:20 major revision (majrev) ? ro. major revision number of the sata capability pointer implemented. 19:16 minor revision (minrev) ? ro. minor revision number of the sata capability pointer implemented. 15:8 next capability pointer (next) ? rwo. points to the ne xt capability structure. 7:0 capability id (cap) ? ro. the value of 12h has been assigned by the pci sig to designate the sata capability pointer. bit description 31:16 reserved. 15:4 bar offset (barofst) ? ro. indicates the offset into the bar where the index/data pair are located (in dword granularity). the index and data i/o registers are located at offset 10h within the i/o sp ace defined by lbar (bar4). a value of 004h indicates offset 10h. 3:0 bar location (barloc) ? ro. indicates the absolute pci configuration register address of the bar containing the index/da ta pair (in dword granularity). the index and data i/o registers reside within the space defined by lbar (bar4) in the sata controller. a value of 8h indicates and offset of 20h, which is lbar (bar4). bit description 15:8 next capability pointer ? ro. a value of 00h indicates th e final item in the capability list. 7:0 capability id ? ro. the value of this field de pends on the flrcssecl bit. if flrcssel = 0, this field is 13h if flrcssel = 1, this field is 09h, indicating vendor specific capability. http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f5) 578 datasheet 15.1.34 flrclv? flr capability le ngth and value (sata?d31:f5) address offset: b2h-b3h attribute: ro, rwo default value: 2006h size: 16 bits function level reset: no (bits 9:8 only) when flrcssel = ?0?, this register is defined as follows. when flrcssel = ?1? , this register is defined as follows. 15.1.35 flrctrl? flr control (sata?d31:f5) address offset: b4h-b5h attribute: r/w, ro default value: 0000h size: 16 bits bit description 15:10 reserved. 9 flr capability ? rwo. this field indicates su pport for function level reset. 8 txp capability ? rwo. this field indicates support for the transactions pending (txp) bit. txp must be supported if flr is supported. 7:0 capability length ? ro. this field indicates the nu mber of bytes of the vendor specific capability as required by the pci spec. it has the value of 06h for flr capability. bit description 15:12 vendor specific capability id ? ro. a value of 02h identifies this capability as a function level reset. 11:8 capability version ? ro. this field indicates the version of the flr capability. 7:0 capability length ? ro. this field indicates the nu mber of bytes of the vendor specific capability as required by the pci spec. it has the value of 06h for flr capability. bit description 15:9 reserved. 8 transactions pending (txp) ? ro. 0 = completions for all non-po sted requests have been re ceived by the controller. 1 = controller has issued non-posted request which has not been completed. 7:1 reserved. 0 initiate flr ? r/w. used to initiate flr transition. a write of ?1? indicates flr transition. http://www..net/ datasheet pdf - http://www..net/ datasheet 579 sata controller registers (d31:f5) 15.1.36 atc?apm trapping cont rol register (sata?d31:f5) address offset: c0h attribute: r/w default value: 00h size: 8 bits note: this sata controller does not support legacy i/o access. therefore, this register is reserved. software shall not change the default values of the register; otherwise the result will be undefined. . 15.1.37 atc?apm trapping control (sata?d31:f5) address offset: c4h attribute: r/wc default value: 00h size: 8 bits note: this sata controller does not support legacy i/o access. therefore, this register is reserved. software shall not change the default values of the register; otherwise the result will be undefined. . bit description 7:0 reserved bit description 7:0 reserved http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f5) 580 datasheet 15.2 bus master ide i/ o registers (d31:f5) the bus master ide function uses 16 bytes of i/o space, allocated via the bar register, located in device 31:function 2 configuration space, offset 20h. all bus master ide i/o space registers can be accessed as byte, word, or dword quantities. reading reserved bits returns an indeterminate, inconsistent va lue, and writes to reserved bits have no affect (but should not be attempted). these registers are only used for legacy operation. software must not use these registers when running ahci. the description of the i/o registers is shown in ta b l e 1 5 - 2 . table 15-2. bus master ide i/o register address map bar+ offset mnemonic register default type 00 bmicp command register primary 00h r/w 01 ? reserved ? ro 02 bmisp bus master ide status register primary 00h r/w, r/wc, ro 03 ? reserved ? ro 04?07 bmidp bus master ide descriptor table pointer primary xxxxxxxxh r/w 08 bmics command register secondary 00h r/w 09 ? reserved ? ro 0ah bmiss bus master ide status register secondary 00h r/w, r/wc, ro 0bh ? reserved ? ro 0ch?0fh bmids bus master ide descriptor table pointer secondary xxxxxxxxh r/w http://www..net/ datasheet pdf - http://www..net/ datasheet 581 sata controller registers (d31:f5) 15.2.1 bmic[p,s]?bus master id e command register (d31:f5) address offset: primary: bar + 00h attribute: r/w secondary: bar + 08h default value: 00h size: 8 bits bit description 7:4 reserved. 3 read / write control (r/wc) ? r/w. this bit sets the di rection of the bus master transfer: this bit must not be changed wh en the bus master function is active. 0 = memory reads 1 = memory writes 2:1 reserved. 0 start/stop bus master (start) ? r/w. 0 = all state information is lost when this bit is cleared. master mode operation cannot be stopped and then resumed. if this bit is reset while bus master operation is still active (i.e., the bus master ide active bit (d31:f5:bar + 02h, bit 0) of the bus master ide status register for that ide channel is set) and the drive has not yet finished its data transfer (the interrupt bi t in the bus master id e status register for that ide channel is not set), the bus master command is said to be aborted and data transferred from the drive may be discarded instead of being written to system memory. 1 = enables bus master operation of the controller. bus master operation does not actually start unless the bus master enable bit (d31:f1:04h, bit 2) in pci configuration space is also set. bus master operation begins when this bit is detected changing from 0 to 1. the controller will transfer data between the ide device and memory only when this bit is set. master operation can be halted by writing a 0 to this bit. note: this bit is intended to be cleared by software after the data transfer is completed, as indicated by either the bu s master ide active bit being cleared or the interrupt bit of the bus master ide status register fo r that ide channel being set, or both. hardware does not clea r this bit automatically. if this bit is cleared to 0 prior to the dma data transfer being initiated by the drive in a device to memory data transfer, then the ich10 will not send dmat to terminate the data transfer. sw interventi on (e.g. sending srst) is required to reset the interface in this condition. http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f5) 582 datasheet 15.2.2 bmis[p,s]?bus master id e status register (d31:f5) address offset: primary: bar + 02h attribute: r/w, r/wc, ro secondary: bar + 0ah default value: 00h size: 8 bits 15.2.3 bmid[p,s]?bus master id e descriptor table pointer register (d31:f5) address offset: primary: bar + 04h?07h attribute: r/w secondary: bar + 0ch ? 0fh default value: all bits undefined size: 32 bits bit description 7 prd interrupt status (prdis) ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = this bit is set when the host controller execution of a prd that has its prd_int bit set. 6 reserved. 5 drive 0 dma capable ? r/w. 0 = not capable 1 = capable. set by device dependent code (b ios or device driver ) to indicate that drive 0 for this channel is capable of dm a transfers, and that the controller has been initialized for optimum performance. the ich10 does not use this bit. it is intended for systems that do no t attach bmide to the pci bus. 4:3 reserved. 2 interrupt ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = set when a device fis is received with the ?i? bit set, provided that software has not disabled interrupts via the ien bit of the device control register (see chapter 5 of the serial ata specification , revision 1.0a). 1 error ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = this bit is set when the controller encoun ters a target abort or master abort when transferring data on pci. 0 bus master ide active (act) ? ro. 0 = this bit is cleared by the ich10 when th e last transfer for a region is performed, where eot for that region is set in the regi on descriptor. it is also cleared by the ich10 when the start bus master bit (d31:f5:bar+ 00h, bit 0) is cleared in the command register. when this bi t is read as a 0, all data transferred from the drive during the previous bus master command is visible in system memory, unless the bus master command was aborted. 1 = set by the ich10 when the start bit is written to the command register. bit description 31:2 address of descriptor table (addr) ? r/w. the bits in this field correspond to bits [31:2] of the memory location of the physic al region descriptor (prd). the descriptor table must be dword-aligned. the descriptor table must no t cross a 64-k boundary in memory. 1:0 reserved http://www..net/ datasheet pdf - http://www..net/ datasheet 583 sata controller registers (d31:f5) 15.3 serial ata index/data pair superset registers all of these i/o registers are in the core we ll. they are exposed only when scc is 01h (i.e. ide programming interface) and the controller is not in combined mode. these are index/data pair registers that are used to access the serialata superset registers (serialata status, serialata control and serialata error). the i/o space for these registers is allocated through sidpba. locations with offset from 08h to 0fh are reserved for future expansion. software-write operations to the reserved locations shall have no effect while software-read operations to the reserved locations shall return 0. 15.3.1 sindx?sata index register (d31:f5) address offset: sidpba + 00h attribute: r/w default value: 00000000h size: 32 bits note: these are index/data pair registers that are used to access the ssts, sctl, and serr. the i/o space for these registers is allocated through sidpba. 15.3.2 sdata?sata index data register (d31:f5) address offset: sidpba + 04h attribute: r/w default value: all bits undefined size: 32 bits note: these are index/data pair registers that are used to access the ssts, sctl, and serr. the i/o space for these registers is allocated through sidpba. bit description 31:16 reserved 15:8 port index (pidx) ? r/w : this index field is used to specify the port of the sata controller at which the po rt-specific ssts, sctl, and serr registers are located. 00h = primary master (port 4) 02h = secondary master (port 5) all other values are reserved. 7:0 register index (ridx) ? r/w : this index field is used to specify one out of three registers currently being indexed into. 00h = ssts 01h = sctl 02h = serr all other values are reserved bit description 31:0 data (data) ? r/w : this data register is a ?window? through which data is read or written to the memory mapped regi sters. a read or write to this data register triggers a corresponding read or write to the memory mapped register poin ted to by the index register. the index register must be setup prior to the read or write to this data register. note that a physical register is not actually implemented as the data is actually stored in the memory mapped registers. since this is not a physical register, the ?default? value is the same as the default value of the register pointed to by index. http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f5) 584 datasheet 15.3.2.1 pxssts?serial ata status register (d31:f5) address offset: attribute: ro default value: 00000000h size: 32 bits sdata when sindx.ridx is 00h. this is a 32-bit register that conveys the current state of the interface and host. the ich10 updates it continuously and asynchronously. when the ich10 transmits a comreset to the device , this register is updated to its reset values. bit description 31:12 reserved 11:8 interface power management (ipm) ? ro . indicates the current interface state: all other values reserved. 7:4 current interface speed (spd) ? ro. indicates the negotiated interface communication speed. all other values reserved. ich10 supports generation 1 communication rates (1.5 gb/s) and gen 2 rates (3.0 gb/s). 3:0 device detection (det) ? ro . indicates the interface device detection and phy state: all other values reserved. value description 0h device not present or communication not established 1h interface in active state 2h interface in partial power management state 6h interface in slumber power management state value description 0h device not present or communication not established 1h generation 1 communication rate negotiated 2h generation 2 communication rate negotiated value description 0h no device de tected and phy communication not established 1h device presence detected but phy communication not established 3h device presence detected and phy communication established 4h phy in offline mode as a result of the interface being disabled or running in a bist loopback mode http://www..net/ datasheet pdf - http://www..net/ datasheet 585 sata controller registers (d31:f5) 15.3.2.2 pxsctl ? serial ata control register (d31:f5) address offset: attribute: r/w, ro default value: 00000004h size: 32 bits sdata when sindx.ridx is 01h. this is a 32-bit read-write register by which software controls sata capabilities. writes to the sc ontrol register result in an action being taken by the ich10 or the interface. reads from the register return the last value written to it. bit description 31:20 reserved 19:16 port multiplier port (pmp) ? ro. this field is not used by ahci. 15:12 select power management (spm) ? ro . this field is no t used by ahci. 11:8 interface power management transitions allowed (ipm) ? r/w . indicates which power states the ich10 is allowed to transition to: all other values reserved 7:4 speed allowed (spd) ? r/w. indicates the highest allowable speed of the interface. this speed is limited by the ca p.iss (abar+00h:bit 23:20) field. all other values reserved. ich10 supports generation 1 communication rates (1.5 gb/s) and gen 2 rates (3.0 gb/s). 3:0 device detection initialization (det) ? r/w . controls the ich10? s device detection and interface initialization. all other values reserved. when this field is written to a 1h, the ich10 initiates comreset and starts the initialization process. when the initialization is complete, this field shall remain 1h until set to another value by software. this field may only be changed to 1h or 4h when pxcmd.st is 0. changing this field while the ich10 is running re sults in undefined behavior. value description 0h no interface restrictions 1h transitions to the partial state disabled 2h transitions to the slumber state disabled 3h transitions to both partial and slumber states disabled value description 0h no speed negotiation restrictions 1h limit speed negotiation to generation 1 communication rate 2h limit speed negotiation to generation 2 communication rate value description 0h no device detection or initialization action requested 1h perform interface communication initialization sequence to establish communication. this is fu nctionally equivalent to a hard reset and results in the interface being reset and communications re-initialized 4h disable the serial ata interface and put phy in offline mode http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f5) 586 datasheet 15.3.2.3 pxserr?serial ata error register (d31:f5) address offset: attribute: r/wc default value: 00000000h size: 32 bits sdata when sindx.ridx is 02h. bits 26:16 of this register contains diagno stic error information for use by diagnostic software in validating correct operation or isolating failure modes. bits 11:0 contain error information used by host software in determining the appropriate response to the error condition. if one or more of bits 11:8 of this register are set, the controller will stop the current transfer. bit description 31:27 reserved 26 exchanged (x) ? r/wc. when set to one this bit indicates that a change in device presence has been detected since the last time this bit was cleared. this bit shall always be set to 1 an ytime a cominit signal is received. this bit is reflected in the p0is.pcs bit. 25 unrecognized fis type (f) ? r/wc. indicates that one or more fiss were received by the transport layer with good crc, but had a type field that was not recognized. 24 transport state transition error (t) ? r/wc. indicates that an error has occurred in the transition from one state to another within the transp ort layer since the last time this bit was cleared. 23 transport state transition error (t) ? r/wc. indicates that an error has occurred in the transition from one state to another within the transport layer since the last time this bit was cleared. 22 handshake (h) ? r/wc. indicates that one or more r_err handshake response was received in response to fram e transmission. such errors may be the result of a crc error detected by the recipien t, a disparity or 8b/10b deco ding error, or other error condition leading to a negative handshake on a transmitted frame. 21 crc error (c) ? r/wc. indicates that one or more crc errors occurred with the link layer. 20 disparity error (d) ? r/wc. this field is not used by ahci. 19 10b to 8b decode error (b) ? r/wc. indicates that one or more 10b to 8b decoding errors occurred. 18 comm wake (w) ? r/wc. indicates that a comm wake signal was detected by the phy. 17 phy internal error (i) ? r/wc. indicates that the phy detected some internal error. 16 phyrdy change (n) ? r/wc. when set to 1 this bit indicates that the internal phyrdy signal changed state since the last time this bit was cleared. in the ich10, this bit will be set when phyrdy changes fro m a 0 -> 1 or a 1 -> 0. the state of this bit is then reflected in the pxis.prcs interrupt status bit and an interrupt will be generated if enabled. software cl ears this bit by writing a 1 to it. 15:12 reserved 11 internal error (e) ? r/wc. the sata controller failed due to a master or target abort when attempting to access system memory. 10 protocol error (p) ? r/wc. a violation of the serial ata protocol was detected. note: the ich10 does not set this bit for all protocol violations th at may occur on the sata link. http://www..net/ datasheet pdf - http://www..net/ datasheet 587 sata controller registers (d31:f5) 9 persistent communication or data integrity error (c) ? r/wc. a communication error that was not recovered occurred that is expected to be persistent. persistent communications errors may arise from faulty interconnect with the device, from a device that has been removed or has failed, or a number of other causes. 8 transient data integrity error (t) ? r/wc. a data integrity error occurred that was not recovered by the interface. 7:2 reserved. 1 recovered communications error (m) ? r/wc. communicat ions between the device and host was temporarily lost but was re-established. this can arise from a device temporarily being removed, from a te mporary loss of phy synchronization, or from other causes and may be derived from the phynrdy signal between the phy and link layers. 0 recovered data integrity error (i) ? r/wc. a data integrit y error occurred that was recovered by the interface through a re try operation or other recovery action. bit description http://www..net/ datasheet pdf - http://www..net/ sata controller registers (d31:f5) 588 datasheet http://www..net/ datasheet pdf - http://www..net/ datasheet 589 uhci controllers registers 16 uhci controllers registers 16.1 pci configuration registers (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) note: the usb functions may be hidden based on th e value of the corresponding bits in the function disable register (see chipset configuration registers). uhcis must be disabled from highest number to lowest within their specific pci device. note: register address locations that are not shown in table 16-2 should be treated as reserved (see section 9.2 for details). table 16-1. uhci controlle r pci configuration map uhci pci device:function notes uhci #1 d29:f0 uhci #2 d29:f1 uhci #3 d29:f2 uhci #4 d26:f0 uhci #5 d26:f1 uhci #6 d26:f2 or d29:f3 d26:f2 can be configured as d29:f3 during bios post. table 16-2. uhci controller pci register address map (usb?d29:f0/f1/f2/f3, d26:f0/ f1/f2) offset mnemonic register name uhci #1-6 default type 00?01h vid vendor identification 8086h ro 02?03h did device identification see register description ro 04?05h pcicmd pci command 0000h r/w, ro 06?07h pcists pci status 0290h r/wc, ro 08h rid revision identification see register description ro 09h pi programming interface 00h ro 0ah scc sub class code 03h ro 0bh bcc base class code 0ch ro 0dh mlt master latency timer 00h ro 0eh headtyp header type see register description ro 20?23h base base address 00000001h r/w, ro 2c?2dh svid subsystem vendor identification 0000h r/wo 2e?2fh sid subsystem identification 0000h r/wo 34h cap_ptr capabiliti es pointer 50h r/wo http://www..net/ datasheet pdf - http://www..net/ uhci controllers registers 590 datasheet note: refer to the intel ? i/o controller hub 10 (ich10) family specification update for the value of the revision id register. 16.1.1 vid?vendor identi fication register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) address offset: 00h?01h attribute: ro default value: 8086h size: 16 bits 16.1.2 did?device identi fication register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) address offset: 02h?03h attribute: ro default value: see bit description size: 16 bits 3ch int_ln interrupt line 00h r/w 3dh int_pn interrupt pin see register description ro 50h flrcid flr capability id 09h ro 51h flrncp flr next capability pointer 00h ro 52?53h flrclv flr capability length and version 2006h ro 54h flrctrl flr control 00h r/w 55h flrstat flr status 00h ro 60h usb_relnum serial bus release number 10h ro c0?c1h usb_legkey usb legacy keyboard/mouse control 2000h r/w, ro r/wc c4h usb_res usb resume enable 00h r/w c8h cwp core well policy 00h r/w cah ucr1 uhci configuration register 1 01h r/w table 16-2. uhci controller pci register address map (usb?d29:f0/f1/f2/f3, d26:f0/ f1/f2) offset mnemonic register name uhci #1-6 default type bit description 15:0 vendor id ? ro. this is a 16-bit value assigned to intel bit description 15:0 device id ? ro. this is a 16-bit value assigned to the intel ? ich10 usb universal host controllers. refer to the intel ? i/o controller hub (ich10) family for the value of the device id register. http://www..net/ datasheet pdf - http://www..net/ datasheet 591 uhci controllers registers 16.1.3 pcicmd?pci command re gister (usb?d29:f0/f1/f2/ f3, d26:f0/f1/f2) address offset: 04h?05h attribute: r/w, ro default value: 0000h size: 16 bits bit description 15:11 reserved 10 interrupt disable ? r/w. 0 = enable. the function is able to generate its interrupt to the interrupt controller. 1 = disable. the function is not capable of genera ting interrupts. the corresponding interrupt status bit is not affected by the interrupt enable. 9 fast back to back enable (fbe) ? ro. hardwired to 0. 8 serr# enable ? ro. reserved as 0. 7 wait cycle control (wcc) ? ro. hardwired to 0. 6 parity error response (per) ? ro. hardwired to 0. 5 vga palette snoop (vps) ? ro. hardwired to 0. 4 postable memory write enable (pmwe) ? ro. hardwired to 0. 3 special cycle enable (sce) ? ro. hardwired to 0. 2 bus master enable (bme) ? r/w. 0 = disable 1 = enable. ich10 can act as a master on the pci bus for usb transfers. 1 memory space enable (mse) ? ro. hardwired to 0. 0 i/o space enable (iose) ? r/w. this bit controls access to the i/o space registers. 0 = disable 1 = enable accesses to the usb i/o registers. the base address register for usb should be programmed before this bit is set. http://www..net/ datasheet pdf - http://www..net/ uhci controllers registers 592 datasheet 16.1.4 pcists?pci status register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) address offset: 06h?07h attribute: r/wc, ro default value: 0290h size: 16 bits note: for the writable bits, software must write a 1 to clear bits that are set. writing a 0 to the bit has no effect. 16.1.5 rid?revision iden tification register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) offset address: 08h attribute: ro default value: see bit description size: 8 bits bit description 15 detected parity error (dpe) ? r/wc. 0 = no parity error detected. 1 = set when a data parity error data parity error is detected on writes to the uhci register space or on read completion s returned to the host controller. 14 reserved. 13 received master abort (rma) ? r/wc. 0 = no master abort generated by usb. 1 = usb, as a master, gene rated a master abort. 12 reserved. 11 signaled target abort (sta) ? r/wc. 0 = ich10 did not terminate transaction for usb function with a target abort. 1 = usb function is targeted with a transaction that the ich10 terminates with a target abort. 10:9 devsel# timing status (dev_sts) ? ro. this 2-bit field defines the timing for devsel# assertion. these read only bits indicate the ich10's devsel# timing when performing a positive decode. ich10 genera tes devsel# with medi um timing for usb. 8 data parity error detected (dped) ? ro. hardwired to 0. 7 fast back to back capable (fb2bc) ? ro. hardwired to 1. 6 user definable features (u df) ? ro. hardwired to 0. 5 66 mhz capable ? ro. hardwired to 0. 4 capabilities list ? ro. hardwired to 1. in dicates that offset 34h contains a valid capabilities pointer. 3 interrupt status ? ro. this bit reflects the state of this func tion?s interrupt at the input of the enable/disable logic. 0 = interrupt is deasserted. 1 = interrupt is asserted. the value reported in this bit is independen t of the value in the interrupt enable bit. 2:0 reserved bit description 7:0 revision id ? ro. refer to the intel ? i/o controller hub (ich10) family specification update for the value of the revision id register http://www..net/ datasheet pdf - http://www..net/ datasheet 593 uhci controllers registers 16.1.6 pi?programming interface register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) address offset: 09h attribute: ro default value: 00h size: 8 bits 16.1.7 scc?sub class code register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) address offset: 0ah attribute: ro default value: 03h size: 8 bits 16.1.8 bcc?base clas s code register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) address offset: 0bh attribute: ro default value: 0ch size: 8 bits 16.1.9 mlt?master latency timer register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) address offset: 0dh attribute: ro default value: 00h size: 8 bits bit description 7:0 programming interface ? ro. 00h = no specific register level programming interface defined. bit description 7:0 sub class code (scc) ? ro. 03h = usb host controller. bit description 7:0 base class code (bcc) ? ro. 0ch = serial bus controller. bit description 7:0 master latency timer (mlt) ? ro. the usb co ntroller is implemented internal to the ich10 and not arbitrated as a pci device. therefore the device does not require a master latency timer. http://www..net/ datasheet pdf - http://www..net/ uhci controllers registers 594 datasheet 16.1.10 headtyp?header type register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) address offset: 0eh attribute: ro default value: see bit description size: 8 bits for uhci #2, 3, 5 and 6 this register is ha rdwired to 00h. for uhci #1 and uhci #4, bit 7 is determined by the values in the usb function disable bits (11:8 of the function disable register chipset config registers:offset 3418h). 16.1.11 base?base address register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) address offset: 20h?23h attribute: r/w, ro default value: 00000001h size: 32 bits 16.1.12 svid ? subsys tem vendor identi fication register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) address offset: 2ch?2dh attribute: r/wo default value: 0000h size: 16 bits lockable: no power well: core function level reset: no bit description 7 multi-function device ? ro. since the upper functi ons in this device can be individually hidden, this bit is based on the function-disab le bits in chipset config space: offset 3418h as follows: 0 = single-function device. (def ault for uhci #2, 3, 5 and 6) 1 = multi-function device. (d efault for uhci #1 and 4) 6:0 configuration layout. hardwired to 00h, whic h indicates the standard pci configuration layout. bit description 31:16 reserved 15:5 base address ? r/w. bits [15:5] correspond to i/o address signals ad [15:5], respectively. this gives 32 bytes of relocatable i/o space. 4:1 reserved 0 resource type indicator (rte) ? ro. hardwire d to 1 to indicate that the base address field in this register maps to i/o space. bit description 15:0 subsystem vendor id (svid) ? r/wo. bios sets the value in this register to identify the subsystem vendor id. the usb_svid register, in combination with the usb subsystem id register, enable s the operating system to distinguish each subsystem from the others. note: the software can write to this register only once per core well reset. writes should be done as a single, 16-bit cycle. http://www..net/ datasheet pdf - http://www..net/ datasheet 595 uhci controllers registers 16.1.13 sid ? subsystem id entification register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) address offset: 2eh ? 2fh attribute: r/wo default value: 0000h size: 16 bits lockable: no power well: core function level reset: no 16.1.14 cap_ptr?capabilities pointer (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) address offset: 34h attribute: r/wo default value: 50h size: 8 bits function level reset: no 16.1.15 int_ln?interrupt line register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) address offset: 3ch attribute: r/w default value: 00h size: 8 bits function level reset: no bit description 15:0 subsystem id (sid) ? r/wo. bios sets the value in this register to identify the subsystem id. the sid register, in combination with the svid register (d29:f0/f1/f2/ f3, d26:f0/f1/f2:2c), enables the operating system to distinguish each subsystem from other(s). the value read in this register is the same as what was written to the ide_sid register. note: the software can write to this register only once per core well reset. writes should be done as a single, 16-bit cycle. bit description 7:0 capability pointer (cap_ptr) ? r/wo. this register points to the next capability in the function level reset capability structure. bit description 7:0 interrupt line (int_ln) ? ro. this data is not used by the ich10. it is to communicate to software the interrupt line that the interrupt pin is connected to. http://www..net/ datasheet pdf - http://www..net/ uhci controllers registers 596 datasheet 16.1.16 int_pn?interrupt pin register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) address offset: 3dh attribute: ro default value: see description size: 8 bits 16.1.17 flrcid?function level reset capability id (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) address offset: 50h attribute: ro default value: 09h size: 8 bits 16.1.18 flrncp?function level re set next capability pointer (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) address offset: 51h attribute: ro default value: 00h size: 8 bits bit description 7:0 interrupt line (int_ln) ? ro. this value tells the soft ware which interrupt pin each usb host controller uses. the upper 4 bits are hardwired to 0000b; the lower 4 bits are determine by the interrupt pin default values that are programmed in the memory- mapped configuration space as follows: uhci #1 - d29ip.u0p (chipset config registers:offset 3108:bits 3:0) uhci #2 - d29ip.u1p (chipset config registers:offset 3108:bits 7:4) uhci #3 - d29ip.u2p (chipset config registers:offset 3108:bits 11:8) uhci #4 - d26ip.u0p (chipset config registers:offset 3114:bits 3:0) uhci #5 - d26ip.u1p (chipset config registers:offset 3114:bits 7:4) uhci #6 - d26ip.u2p (chipset config registers:offset 3114:bits 11:8) or uhci #6 - d29ip.u3p (chipset config registers:offset 3108:bits 15:12) note: this does not determine the mapping to the pirq pins. bit description 7:0 capability id ? ro. 13h = if flrcssel = 0 09h (vendor specific capability) = if flrcssel = 1 bit description 7:0 a value of 00h indicates that this is the last capability field. http://www..net/ datasheet pdf - http://www..net/ datasheet 597 uhci controllers registers 16.1.19 flrclv?function level re set capability length and version (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) address offset: 52h-53h attribute: ro, r/wo default value: 2006h size: 16 bits when flrcssel = 0, this register is defined as follows: when flrcssel = 1, this register is defined as follows: 16.1.20 usb_flrctrl?flr control register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) address offset: 54h attribute: r/w default value: 00h size: 8 bits bit description 15:10 reserved. 9 flr capability ? r/wo. 1 = support for function level reset (flr). 8 txp capability ? r/wo. 1 = support for transactions pending (txp) bit. txp must be supported if flr is supported. 7:0 capability length ? ro. this field indicates the # of bytes of this vendor specific capability as required by the pci specificat ion. it ha?s the value of 06h for the flr capability. bit description 15:12 vendor specific capability id ? ro. a value of 02h in this field identifies this capability a?s function level reset. 11:8 capability version ? ro. this field indicates the version of the flr capability. 7:0 capability length ? ro. this field indicates the # of bytes of this vendor specific capability as required by the pci specificat ion. it ha?s the value of 06h for the flr capability. bit description 7:1 reserved. 0 initiate flr ? r/w. used to initiate flr transition. a write of ?1? initiates flr transition. since hardware must not respond to any cycles until flr completion, the value read by software from this bit i always ?0?. http://www..net/ datasheet pdf - http://www..net/ uhci controllers registers 598 datasheet 16.1.21 usb_flrstat?flr status register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) address offset: 55h attribute: ro default value: 00h size: 8 bits 16.1.22 usb_relnum?serial bus release number register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) address offset: 60h attribute: ro default value: 10h size: 8 bits 16.1.23 usb_legkey?usb legacy keyboard/mouse control register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) address offset: c0h?c1h attribute: r/w, r/wc, ro default value: 2000h size: 16 bits function level reset:no this register is implemented separately in each of the usb uhci functions. however, the enable and status bits for the trapping logic are or?d and shared, respectively, since their functionality is not spec ific to any one host controller. bit description 7:1 reserved. 0 transaction pending (txp) ? ro. 0 = indicates completions for all non-po sted requests have been received. 1 = indicates the controller has issued non-posted request which have not been completed. bit description 7:0 serial bus release number ? ro. 10h = usb controller supports the usb specification , release 1.0. bit description 15 smi caused by end of pa ss-through (smibyendps) ? r/wc. this bit indicates if the event occurred. note that even if the co rresponding enable bit is not set in bit 7, then this bit will still be active. it is up to the smm code to use the enable bit to determine the exact cause of the smi#. 0 = software clears this bit by writing a 1 to the bit location in any of the controllers. 1 = event occurred 14 reserved 13 pci interrupt enable (usbpirqen) ? r/w. this bit is used to prevent the usb controller from generating an interrupt due to transactions on its ports. note that, when disabled, it will probably be configured to generate an smi using bi t 4 of this register. default to 1 for compatibilit y with older usb software. 0 = disable 1 = enable http://www..net/ datasheet pdf - http://www..net/ datasheet 599 uhci controllers registers 12 smi caused by usb interrupt (smibyusb) ? ro. this bit indicates if an interrupt event occurred from this controll er. the interrupt from the cont roller is taken before the enable in bit 13 has any effect to create th is read-only bit. note that even if the corresponding enable bit is not set in bit 4, th is bit may still be active. it is up to the smm code to use the enable bit to determine the exact cause of the smi#. 0 = software should clear the interrupts via th e usb controllers. writing a 1 to this bit will have no effect. 1 = event occurred. 11 smi caused by port 64 write (trapby64w) ? r/wc. this bit indicates if the event occurred. note that even if the corresponding en able bit is not set in bit 3, this bit will still be active. it is up to the smm code to use the enable bit to determine the exact cause of the smi#. note that the a20gate pass-through logic allows specific port 64h writes to complete without setting this bit. 0 = software clears this bit by writing a 1 to the bit location in any of the controllers. 1 = event occurred. 10 smi caused by port 64 read (trapby64r) ? r/wc. this bit indicates if the event occurred. note that even if the corresponding en able bit is not set in bit 2, this bit will still be active. it is up to the smm code to use the enable bit to determine the exact cause of the smi#. 0 = software clears this bit by writing a 1 to the bit location in any of the controllers. 1 = event occurred. 9 smi caused by port 60 write (trapby60w) ? r/wc. this bit indicates if the event occurred. note that even if the corresponding en able bit is not set in bit 1, this bit will still be active. it is up to the smm code to use the enable bit to determine the exact cause of the smi#. note that the a20gate pass-through logic allows specific port 64h writes to complete without setting this bit. 0 = software clears this bit by writing a 1 to the bit location in any of the controllers. 1 = event occurred. 8 smi caused by port 60 read (trapby60r) ? r/wc. this bit indicates if the event occurred. note that even if the corresponding enable bit is not set in the bit 0, then this bit will still be active. it is up to the sm m code to use the enable bit to determine the exact cause of the smi#. 0 = software clears this bit by writing a 1 to the bit location in any of the controllers. 1 = event occurred. 7 smi at end of pass-through enable (smiatendps) ? r/w. this bit enables smi at the end of a pass-through. this can occur if an smi is generated in the middle of a pass-through, and needs to be serviced later. 0 = disable 1 = enable 6 pass through state (pstate) ? ro. 0 = if software needs to reset this bit, it should set bit 5 in all of the host controllers to 0. 1 = indicates that the state machine is in the middle of an a20gate pass-through sequence. 5 a20gate pass-through enable (a20passen) ? r/w. 0 = disable. 1 = enable. allows a20gate sequence pass-through function. a specific cycle sequence involving writes to port 60h and 64h does no t result in the setting of the smi status bits. 4 smi on usb irq enable (usbsmien) ? r/w. 0 = disable 1 = enable. usb interrupt will cause an smi event. bit description http://www..net/ datasheet pdf - http://www..net/ uhci controllers registers 600 datasheet 16.1.24 usb_res?usb resu me enable register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) address offset: c4h attribute: r/w default value: 00h size: 8 bits function level reset:no 3 smi on port 64 writes enable (64wen) ? r/w. 0 = disable 1 = enable. a 1 in bit 11 will cause an smi event. 2 smi on port 64 reads enable (64ren) ? r/w. 0 = disable 1 = enable. a 1 in bit 10 will cause an smi event. 1 smi on port 60 writes enable (60wen) ? r/w. 0 = disable 1 = enable. a 1 in bit 9 will cause an smi event. 0 smi on port 60 reads enable (60ren) ? r/w. 0 = disable 1 = enable. a 1 in bit 8 will cause an smi event. bit description bit description 7:2 reserved 1 port1en ? r/w. enable port 1 of the usb controller to respond to wakeup events. 0 = the usb controller will not look at this port for a wakeup event. 1 = the usb controller will monitor this port for remote wakeup and connect/ disconnect events. 0 port0en ? r/w. enable port 0 of the usb controller to respond to wakeup events. 0 = the usb controller will not look at this port for a wakeup event. 1 = the usb controller will monitor this port for remote wakeup and connect/ disconnect events. http://www..net/ datasheet pdf - http://www..net/ datasheet 601 uhci controllers registers 16.1.25 cwp?core well policy register (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) address offset: c8h attribute: r/w default value: 00h size: 8 bits function level reset: no 16.1.26 ucr1?uchi config uration register 1 (usb?d29:f0/f1/f2/f3, d26:f0/f1/f2) address offset: cah attribute: r/w default value: 01h size: 8 bits bit description 7:3 reserved 2 host controller alignment enable (hcae) ? r/w. setting this bit aligns the host controller?s start of th e first frame to a central 1ms hear tbeat. setting this bit for each controller maintains alignment. 1 hchalted bit read mode (hbm) ? r/w. this bit controls what sw sees on reads of the hchalted bit in the interval between when sw has set the run bit and the first heartbeat. 0 = software reads the delayed value of hchalted (sees a 1 while the controller is waiting for the heartbeat). 1 = software reads the value it would expect to see without the delay (sees a 0 even while the controller is wa iting for the heartbeat). 0 static bus master status policy enable (sbmspe) ? r/w. 0 = the uhci host controller dynamically sets the bus master status bit (power management 1 status register,[pmbase +00h], bit 4) base d on the memory accesses that are schedule d. the default setting pr ovides a more accurate indication of snoopable memory accesses in order to help with software-invoked entry to c3 and c4 power states 1 = the uhci host controller statically forces the bus master st atus bit in power management space to 1 whenever the hchalted bit (usb status register, base+02h, bit 5) is cleared. note: the pci power management registers are enabled in the pci device 31: function 0 space (pm_io_en), and can be moved to any i/o location (128-byte aligned). bit description 7:1 reserved 0 initiator/target arbitration disable (itad) ? r/w. when this bit is set to 1, the uhci controll er will force dma read requests to return prior to completing transactions as a target. when this bit is set to 0, the uhci cont roller will allow completions from target transactions to complete independent of th e state of forward progress of the master. http://www..net/ datasheet pdf - http://www..net/ uhci controllers registers 602 datasheet 16.2 usb i/o registers some of the read/write register bits that deal with changing the state of the usb hub ports function such that on read back they reflect the current state of the port, and not necessarily the state of the last write to the register. this allows the software to poll the state of the port and wait until it is in the proper state before proceeding. a host controller reset, global reset, or port rese t will immediately terminate a transfer on the affected ports and disable the port. this affects the usbcmd register, bit 4 and the portsc registers, bits [12,6,2]. see individual bit descriptions for more detail. note: 1. these registers are word writable only. byte writes to these registers have unpredictable effects. table 16-3. usb i/o registers base + offset mnemonic register name default type 00?01h usbcmd usb command 0000h r/w 02?03h usbsts usb status 0020h r/wc 04?05h usbintr usb interrupt enable 0000h r/w 06?07h frnum frame number 0000h r/w (see note 1) 08?0bh frbaseadd frame list base address undefined r/w 0ch sofmod start of frame modify 40h r/w 0d?0fh ? reserved ? ? 10?11h portsc0 port 0 status/control 0080h r/wc, ro, r/w (see note 1) 12?13h portsc1 port 1 status/control 0080h r/wc, ro, r/w (see note 1) http://www..net/ datasheet pdf - http://www..net/ datasheet 603 uhci controllers registers 16.2.1 usbcmd?usb command register i/o offset: base + (00h?01h) attribute: r/w default value: 0000h size: 16 bits the command register indicates the command to be executed by the serial bus host controller. writing to the register causes a command to be executed. the table following the bit description provides additi onal information on the operation of the run/stop and debug bits. bit description 15:7 reserved 8 loop back test mode ? r/w. 0 = disable loop back test mode. 1 = ich10 is in loop back te st mode. when both ports ar e connected together, a write to one port will be seen on the other port and the data wi ll be stored in i/o offset 18h. 7 max packet (maxp) ? r/w. this bit selects the maximum packet size that can be used for full speed bandwidth reclamation at the end of a frame. this value is used by the host controller to determine whether it should initiate another transaction based on the time remaining in the sof counter. use of reclamation packet s larger than the programmed size will cause a babble error if executed during the critical window at frame end. the babble error results in the o ffending endpoint being stalled. software is responsible for ensuring that any packet which could be executed under bandwidth reclamation be within this size limit. 0 = 32 bytes 1 = 64 bytes 6 configure flag (cf) ? r/w. this bit has no effect on the hardware. it is provided only as a semaphore service for software. 0 = indicates that software has not completed host controller configuration. 1 = hcd software sets this bit as the last action in its process of configuring the host controller. 5 software debug (swdbg) ? r/w. the swdbg bit must only be manipulated when the controller is in the stoppe d state. this can be determin ed by checking the hchalted bit in the usbsts register. 0 = normal mode. 1 = debug mode. in sw debug mode, the host controller clears the run/stop bit after the completion of each usb transaction. the next transaction is executed when software sets the run/stop bit back to 1. 4 force global resume (fgr) ? r/w. 0 = software resets this bit to 0 after 20 ms has elapsed to stop sending the global resume signal. at that time all usb devices should be ready for bus activity. the 1 to 0 transition causes the port to send a low speed eop signal. this bit will remain a 1 until the eop has completed. 1 = host controller sends the global resume si gnal on the usb, and sets this bit to 1 when a resume event (connect, disconnect, or k-state) is detected while in global suspend mode. http://www..net/ datasheet pdf - http://www..net/ uhci controllers registers 604 datasheet 3 enter global suspend mode (egsm) ? r/w. 0 = software resets this bit to 0 to come ou t of global suspend mode. software writes this bit to 0 at the same time that force global resume (bit 4) is written to 0 or after writing bit 4 to 0. 1 = host controller enters the global suspen d mode. no usb transactions occur during this time. the host controller is able to receive resume signals from usb and interrupt the system. software must ensure that the run/stop bit (bit 0) is cleared prior to setting this bit. 2 global reset (greset) ? r/w. 0 = this bit is reset by the software after a minimum of 10 ms has elapsed as specified in chapter 7 of the usb specification. 1 = global reset. the host controller sends the global reset signal on the usb and then resets all its logic, including the internal hub registers. the hu b registers are reset to their power on state. chip hardware re set has the same effect as global reset (bit 2), except that the host controller does not send the global reset on usb. 1 host controller reset (hcreset) ? r/w. the effects of hcrese t on hub registers are slightly different from chip hardware reset and global usb reset. the hcreset affects bits [8,3:0] of the po rt status and control regist er (portsc) of each port. hcreset resets the state machines of th e host controller including the connect/ disconnect state machine (one for each po rt). when the connect/disconnect state machine is reset, the output that signals connect/disconnect are negated to 0, effectively signaling a di sconnect, even if a device is at tached to the port. this virtual disconnect causes the port to be disabled. this disconnect and disabling of the port causes bit 1 (connect status change) and bit 3 (port enable/disable change) of the portsc to get set. the disconnect also caus es bit 8 of portsc to reset. about 64 bit times after hcreset goes to 0, the connect and low-speed de tect will take place, and bits 0 and 8 of the portsc will change accordingly. 0 = reset by the host controller when the reset process is complete. 1 = reset. when this bit is set, the host controll er module resets it s internal timers, counters, state machines, etc. to their initial value. any transaction currently in progress on usb is immediately terminated. 0 run/stop (rs) ? r/w. when set to 1, the ich10 proceeds with execution of the schedule. the ich10 continues execution as long as this bit is set. when this bit is cleared, the ich10 completes the current transaction on the usb and then halts. the hc halted bit in the status register indicate s when the host controller has finished the transaction and has entered the stopped state. the host contro ller clears this bit when the following fatal errors oc cur: consistency check failure, or memory access errors. 0 = stop 1 = run note: this bit should only be cleared if there are no active transaction descriptors in the executable schedule or software will reset the host controller prior to setting this bit again. bit description http://www..net/ datasheet pdf - http://www..net/ datasheet 605 uhci controllers registers when the usb host controller is in software debug mode (usbcmd register bit 5=1), the single stepping software debug operation is as follows: to enter software debug mode: 1. hcd puts host controller in stop state by setting the run/stop bit to 0. 2. hcd puts host controller in debug mode by setting the swdbg bit to 1. 3. hcd sets up the correct command list and start of frame value for starting point in the frame list single step loop. 4. hcd sets run/stop bit to 1. 5. host controller executes next active td, sets run/stop bit to 0, and stops. 6. hcd reads the usbcmd register to check if the single step execution is completed (hchalted=1). 7. hcd checks results of td execution. go to step 4 to execute next td or step 8 to end software debug mode. 8. hcd ends software debug mode by setting swdbg bit to 0. 9. hcd sets up normal command list and frame list table. 10. hcd sets run/stop bit to 1 to resume normal schedule execution. in software debug mode, when the run/stop bit is set, the host controller starts. when a valid td is found, the run/stop bit is reset. when the td is finished, the hchalted bit in the usbsts register (bit 5) is set. the sw debug mode skips over inactive tds an d only halts after an active td has been executed. when the last active td in a frame has been executed, the host controller waits until the next sof is sent and then fetc hes the first td of the next frame before halting. table 16-4. run/stop, debug bit interaction sw dbg (bit 5), run/stop (bit 0) operation swdbg (bit 5) run/stop (bit 0) description 00 if executing a command, the host controller completes the command and then stops. the 1.0 ms frame counter is reset and command list execution resumes from start of frame using the frame list pointer selected by the current value in the frnum register. (while run/ stop=0, the frnum register (bas e + 06h) can be reprogrammed). 01 execution of the command list resumes from start of frame using the frame list pointer selected by the current value in the frnum register. the host controller remains running until the run/stop bit is cleared (by software or hardware). 10 if executing a command, the host controller completes the command and then stops and the 1.0 ms fram e counter is froze n at its current value. all status are preserved. the host controller begins execution of the command list from where it le ft off when the run/stop bit is set. 11 execution of the command list resumes from where the previous execution stopped. the run/stop bit is set to 0 by the host controller when a td is being fetc hed. this causes the ho st controller to stop again after the execution of the td (single step). when the host controller has completed execution, the hc halted bit in the status register is set. http://www..net/ datasheet pdf - http://www..net/ uhci controllers registers 606 datasheet this hchalted bit can also be used outside of software debug mode to indicate when the host controller has detected the run/stop bit and has completed the current transaction. outside of the software debug mode, setting the run/stop bit to 0 always resets the sof counter so that when the run/ stop bit is set the host controller starts over again from the frame list location poin ted to by the frame list index (see frnum register description) rather than continuing where it stopped. 16.2.2 usbsts?usb status register i/o offset: base + (02h?03h) attribute: r/wc default value: 0020h size: 16 bits this register indicates pending interrupts and various states of the host controller. the status resulting from a transaction on the serial bus is not indicated in this register. bit description 15:6 reserved 5 hchalted ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = the host controller has stopped executing as a result of the ru n/stop bit being set to 0, either by software or by the host controller hardware (debug mode or an internal error). default. 4 host controller process error ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = the host controller has detected a fatal e rror. this indicates that the host controller suffered a consistency check failure while processing a transf er descriptor. an example of a consistency check failure woul d be finding an invalid pid field while processing the packet header portion of the td. when this error occurs, the host controller clears the run/stop bit in the command register (d29:f0/f1/f2/f3, d26:f0/f1/f2:base + 00h, bit 0) to prevent further schedule execution. a hardware interrupt is ge nerated to the system. 3 host system error ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = a serious error occurred during a host system access involving the host controller module. in a pci system, conditions that se t this bit to 1 include pci parity error, pci master abort, and pci target abort. wh en this error occurs, the host controller clears the run/stop bit in the command re gister to prevent fu rther execution of the scheduled tds. a hardware interrupt is generated to the system. 2 resume detect (rsm_det) ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = the host controller received a ?resume? signal from a usb de vice. this is only valid if the host controller is in a global suspend state (command register, d29:f0/ f1/f2/f3, d26:f0/f1/f2:base + 00h, bit 3 = 1). 1 usb error interrupt ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = completion of a usb transaction resulted in an error condition (e.g., error counter underflow). if the td on which the erro r interrupt occurred also had its ioc bit (d29:f0/f1/f2/f3, d26:f0/f1/f2:base + 04h, bit 2) set, both this bit and bit 0 are set. 0 usb interrupt (usbint) ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = the host controller sets this bit when the cause of an interrupt is a completion of a usb transaction whose transfer descriptor had its ioc bit set. also set when a short packet is detected (actual length field in td is less than maximum length field in td), and short packet dete ction is enabled in that td. http://www..net/ datasheet pdf - http://www..net/ datasheet 607 uhci controllers registers 16.2.3 usbintr?usb inte rrupt enable register i/o offset: base + (04h?05h) attribute: r/w default value: 0000h size: 16 bits this register enables and disables report ing of the corresponding interrupt to the software. when a bit is set and the corresponding interrupt is active, an interrupt is generated to the host. fatal errors (host controller processor error, (d29:f0/f1/f2, d26:f0/f1:base + 02h, bit 4, usbsts register) cannot be disabled by the host controller. interrupt sources that are disabled in this register still appear in the status register to allow the software to poll for events. 16.2.4 frnum?frame number register i/o offset: base + (06?07h) attribute: r/w (writes must be word writes) default value: 0000h size: 16 bits bits [10:0] of this register contain the cu rrent frame number that is included in the frame sof packet. this register reflects the count value of the internal frame number counter. bits [9:0] are used to select a pa rticular entry in the frame list during scheduled execution. this register is updated at the end of each frame time. this register must be written as a word. by te writes are not supported. this register cannot be written unless the host controller is in the stopped state as indicated by the hchalted bit (d29:f0/f1/f2/f3, d26:f0/f1/f2:base + 02h, bit 5). a write to this register while the run/stop bit is set (d 29:f0/f1/f2/f3, d26:f0/f1/f2:base + 00h, bit 0) is ignored. bit description 15:5 reserved 4 scratchpad (sp) ? r/w. 3 short packet interrupt enable ? r/w. 0 = disabled. 1 = enabled. 2 interrupt on complete enable (ioc) ? r/w. 0 = disabled. 1 = enabled. 1 resume interrupt enable ? r/w. 0 = disabled. 1 = enabled. 0 timeout/crc interrupt enable ? r/w. 0 = disabled. 1 = enabled. bit description 15:11 reserved 10:0 frame list current index/frame number ? r/w. this field provides the frame number in the sof frame. the value in this register increments at the end of each time frame (approximately every 1 ms). in addition, bits [9:0] are used for the frame list current index and correspond to memory address signals [11:2]. http://www..net/ datasheet pdf - http://www..net/ uhci controllers registers 608 datasheet 16.2.5 frbaseadd?frame list base address register i/o offset: base + (08h?0bh) attribute: r/w default value: undefined size: 32 bits this 32-bit register contains the beginnin g address of the frame list in the system memory. hcd loads this register prior to starting the schedule execution by the host controller. when written, only the upper 20 bits are used. the lower 12 bits are written as 0s (4 kb alignment). the contents of this register are combined with the frame number counter to enable the host controller to step through the frame list in sequence. the two least significant bits are always 00. this requires dword-alignment for all list entries. this configuration supports 1024 frame list entries. 16.2.6 sofmod?start of frame modify register i/o offset: base + (0ch) attribute: r/w default value: 40h size: 8 bits this 1-byte register is used to modify the value used in the generation of sof timing on the usb. only the 7 least significant bits are used. when a new value is written into these 7 bits, the sof timing of the next frame will be adjusted. this feature can be used to adjust out any offset from the clock source that generates the clock that drives the sof counter. this register can also be used to maintain real time synchronization with the rest of the system so that all devices have the same sense of real time. using this register, the frame length can be adju sted across the full range required by the usb specification. its initial programmed value is system dependent based on the accuracy of hardware usb clock and is initialized by system bios. it may be reprogrammed by usb system software at any time. its value will take effect from the beginning of the next frame. this register is reset upon a host controller reset or global reset. software must maintain a copy of its value for reprogramming if necessary. bit description 31:12 base address ? r/w. these bits correspond to memory address signals [31:12], respectively. 11:0 reserved bit description 7 reserved 6:0 sof timing value ? r/w. guidelines for the modifica tion of frame time are contained in chapter 7 of the usb specification. the sof cycle time (number of sof counter clock periods to generate a sof frame length) is equal to 11936 + value in this field. the default value is decimal 64 which gives a sof cycle time of 12000. for a 12 mhz sof counter clock input, this produces a 1 ms frame period. the following table indicates what sof timing value to program into this field for a certain frame period. frame lengt h ( # 12 mhz c l oc k s ) (decimal) sof t i m i ng va l ue ( t hi s reg i ster ) (decimal) 11936 0 11937 1 ?? 11999 63 12000 64 12001 65 ?? 12062 126 12063 127 http://www..net/ datasheet pdf - http://www..net/ datasheet 609 uhci controllers registers 16.2.7 portsc[0,1]?port stat us and control register i/o offset: port 0/2/4/6/8/10: base + (10h?11h) attribute: r/wc, ro, port 1/3/5/7/9/11: base + (12h?13h) r/w (word writes only) default value: 0080h size: 16 bits note: for uhci #1 (d29:f0), this applies to ich 10 usb ports 0 and 1; for uhci #2 (d29:f1), this applies to ich10 usb ports 2 and 3; fo r uhci #3 (d29:f2), this applies to ich10 usb ports 4 and 5, for uhci #4 (d26:f0), this applies to ich10 usb ports 6 and 7, for uhci #5 (d26:f1), this applies to ich10 usb ports 8 and 9 and for uhci #6 (d26:f2 or d29:f3), this applies to ich10 usb ports 10 and 11. after a power-up reset, global reset, or host controller reset, the initial conditions of a port are: no device connected, port disabled, and the bus line status is 00 (single- ended 0). port reset and enable sequence when software wishes to reset a usb device it will assert the port reset bit in the port status and control register. the minimum reset signaling time is 10 ms and is enforced by software. to complete the reset sequence, software clears the port reset bit. the intel uhci controller must re-detect the port connect after reset signaling is complete before the controller will allow the port enable bit to de set by software. this time is approximately 5.3 s. software has several possible options to meet the timing requirement and a partial list is enumerated below: ? iterate a short wait, setting the port enab le bit and reading it back to see if the enable bit is set. ? poll the connect status bit and wait for the hardware to recognize the connect prior to enabling the port. ? wait longer than the hardware detect time after clearing the port reset and prior to enabling the port. bit description 15:13 reserved. 12 suspend ? r/w . this bit should not be written to a 1 if global suspend is active (bit 3=1 in the usbcmd register). bit 2 and bit 12 of this register defi ne the hub states as follows: when in suspend state, downst ream propagation of data is blocked on this port, except for single-ended 0 resets (global reset and po rt reset). the blocking occurs at the end of the current transaction, if a transaction wa s in progress when this bit was written to 1. in the suspend state, the port is sensit ive to resume detectio n. note that the bit status does not change until the port is suspended and th at there may be a delay in suspending a port if there is a transa ction currently in pr ogress on the usb. 1 = port in suspend state. 0 = port not in suspend state. note: normally, if a transaction is in progress when this bit is set, the port will be suspended when the current transaction completes. however, in the case of a specific error condition (out transact ion with babble), the ich10 may issue a start-of-frame, and then suspend the port. 11 overcurrent indicator ? r/wc. set by hardware. 0 = software clears this bit by writing a 1 to it. 1 = overcurrent pin has gone from in active to active on this port. bits [12,2] hub state x,0 disable 0, 1 enable 1, 1 suspend http://www..net/ datasheet pdf - http://www..net/ uhci controllers registers 610 datasheet 10 overcurrent active ? ro. this bit is set and cleared by hardware. 0 = indicates that the overcurre nt pin is inactive (high). 1 = indicates that the overcu rrent pin is active (low). 9 port reset ? r/w . 0 = port is not in reset. 1 = port is in reset. when set, the port is disabled and sends the usb reset signaling. 8 low speed device attached (ls) ? ro . 0 = full speed device is attached. 1 = low speed device is attached to this port. 7 reserved ? ro. always read as 1. 6 resume detect (rsm_det) ? r/w. software sets this bit to a 1 to drive resume signaling. the host controller se ts this bit to a 1 if a j-to-k transition is de tected for at least 32 microseconds while the port is in the suspend state. the ich10 will then reflect the k-state back onto the bus as long as the bit remains a 1, and the port is still in the suspend state (bit 12,2 are ?11?). writ ing a 0 (from 1) causes the port to send a low speed eop. this bit will remain a 1 until the eop has completed. 0 = no resume (k-state) de tected/driven on port. 1 = resume detected/driven on port. 5:4 line status ? ro . these bits reflect the d+ (bit 4) an d d? (bit 5) signals lines? logical levels. these bits are used for fault detect an d recovery as well as for usb diagnostics. this field is updated at eo f2 time (see chapter 11 of the usb specification). 3 port enable/disable change ? r/wc . for the root hub, this bit gets set only when a port is disabled due to disc onnect on that port or due to the appropriate conditions existing at the eof2 point (see chapter 11 of the usb specification). 0 = no change. software clears this bi t by writing a 1 to the bit location. 1 = port enabled/disabled status has changed. 2 port enabled/disabled (port_en) ? r/w . ports can be enabled by host software only. ports can be disabled by either a faul t condition (disconnect event or other fault condition) or by host software . note that the bit status does not change until the port state actually changes and that there may be a delay in disabling or enabling a port if there is a transaction currently in progress on the usb. 0 = disable 1 = enable 1 connect status change ? r/wc . this bit indicates that a change has occurred in the port?s current connect status (see bit 0). the hub device se ts this bit for any changes to the port device connect status, even if system software has not cleared a connect status change. if, for example, the insert ion status changes twice before system software has cleared the change d condition, hub hardware wi ll be setting? an already- set bit (i.e., the bit will remain set). however, the hub transfers the change bit only once when the host controller requests a da ta transfer to the status change endpoint. system software is re sponsible for determining state change history in such a case. 0 = no change. software clears th is bit by writing a 1 to it. 1 = change in current connect status. 0 current connect status ? ro . this value reflects the current state of the port, and may not correspond directly to the event th at caused the connect status change bit (bit 1) to be set. 0 = no device is present. 1 = device is present on port. bit description http://www..net/ datasheet pdf - http://www..net/ datasheet 611 ehci controller registers (d29:f7, d26:f7) 17 ehci controller registers (d29:f7, d26:f7) 17.1 usb ehci configuration registers (usb ehci?d29:f7, d26:f7) note: register address locations that are not shown in table 17-1 should be treated as reserved (see section 9.2 for details). table 17-1. usb ehci pci register address ma p (usb ehci?d29:f7, d26:f7) (sheet 1 of 2) offset mnemonic register name default value type 00h?01h vid vendor identification 8086h ro 02h?03h did device identification see register description ro 04h?05h pcicmd pci command 0000h r/w, ro 06h?07h pcists pci status 0290h r/wc, ro 08h rid revision identification see register description ro 09h pi programming interface 20h ro 0ah scc sub class code 03h ro 0bh bcc base class code 0ch ro 0dh pmlt primary master latency timer 00h ro 10h?13h mem_base memory base address 00000000h r/w, ro 2ch?2dh svid usb ehci subsystem vendor identification xxxxh r/w 2eh?2fh sid usb ehci subsystem identification xxxxh r/w 34h cap_ptr capabilities pointer 50h ro 3ch int_ln interrupt line 00h r/w 3dh int_pn interrupt pin see register description ro 50h pwr_capid pci power management capability id 01h ro 51h nxt_ptr1 next item pointer 58h r/w 52h?53h pwr_cap power manageme nt capabilities c9c2h r/w 54h?55h pwr_cntl_sts power management control/ status 0000h r/w, r/wc, ro 58h debug_capid debug port capability id 0ah ro 59h nxt_ptr2 next item pointer #2 98h ro 5ah?5bh debug_base debug port base offset 20a0h ro 60h usb_relnum usb release number 20h ro http://www..net/ datasheet pdf - http://www..net/ ehci controller registers (d29:f7, d26:f7) 612 datasheet note: all configuration registers in this section are in the core well and reset by a core well reset and the d3-to-d0 warm reset, except as noted. 17.1.1 vid?vendor identi fication register (usb ehci?d29:f7, d26:f7) offset address: 00h ? 01h attribute: ro default value: 8086h size: 16 bits 17.1.2 did?device identi fication register (usb ehci?d29:f7, d26:f7) offset address: 02h ? 03h attribute: ro default value: see bit description size: 16 bits 61h fl_adj frame length adjustment 20h r/w 62h?63h pwake_cap port wa ke capabili ties 01ffh r/w 64h?67h ? reserved ? ? 68h?6bh leg_ext_cap usb ehci legacy support extended capability 00000001h r/w, ro 6ch?6fh leg_ext_cs usb ehci legacy extended support control/status 00000000h r/w, r/wc, ro 70h?73h special_smi intel specific usb 2.0 smi 00000000h r/w, r/wc 74h?7fh ? reserved ? ? 80h access_cntl access control 00h r/w 84h ehciir1 ehci initializatio n register 1 01h r/w, rwl 98h flr_cid flr capability id 09h ro 99h flr_next flr next capability pointer 00h ro 9ah-9bh flr_clv flr capability length and version 2006h ro, r/wo 9ch flr_ctrl flr control 00h r/w 9dh flr_stat flr status 00h ro fch ehciir2 ehci initialization register 2 20001706h r/w table 17-1. usb ehci pci register address ma p (usb ehci?d29:f7, d26:f7) (sheet 2 of 2) offset mnemonic register name default value type bit description 15:0 vendor id ? ro. this is a 16-bit value assigned to intel. bit description 15:0 device id ? ro. this is a 16-bit value assigned to the intel ? ich10 usb ehci controller. refer to the intel ? i/o controller hub (ich10) family specification update for the value of the device id register. http://www..net/ datasheet pdf - http://www..net/ datasheet 613 ehci controller registers (d29:f7, d26:f7) 17.1.3 pcicmd?pci co mmand register (usb ehci?d29:f7, d26:f7) address offset: 04h ? 05h attribute: r/w, ro default value: 0000h size: 16 bits bit description 15:11 reserved 10 interrupt disable ? r/w. 0 = the function is capable of genera ting interrupts. 1 = the function can not generate its interrupt to the interrupt controller. note that the corresponding interrupt status bit (d29:f7, d26:f7:06h, bit 3) is not affected by the interrupt enable. 9 fast back to back enable (fbe) ? ro. hardwired to 0. 8 serr# enable (serr_en) ? r/w 0 = disables ehc?s capability to generate an serr#. 1 = the enhanced host controller (ehc) is ca pable of generating (internally) serr# in the following cases: ? when it receives a completion status other than ?successful? for one of its dma -initiated memory reads on dmi (and subseque ntly on its internal interface). ? when it detects an address or command parity error and the parity error response bit is set. ? when it detects a data parity error (when the da ta is going into the eh c) and the parity error response bit is set. 7 wait cycle control (wcc) ? ro. hardwired to 0. 6 parity error response (per) ? r/w. 0 = the ehc is not checking for correct parity (on its internal interface). 1 = the ehc is checking for correct parity (o n its internal interface) and halt operation when bad parity is detect ed during the data phase. note: if the ehc detects bad parity on the addr ess or command phases when the bit is set to 1, the host controller does not take the cycle. it halts the host controller (if currently not halted) and sets the host system error bit in the usbsts register. this applies to both requ ests and completions from the system interface. this bit must be set in order for the parity e rrors to generate serr#. 5 vga palette snoop (vps) ? ro. hardwired to 0. 4 postable memory write enable (pmwe) ? ro. hardwired to 0. 3 special cycle enable (sce) ? ro. hardwired to 0. 2 bus master enable (bme) ? r/w. 0 = disables this functionality. 1 = enables the ich10 to act as a mast er on the pci bus for usb transfers. 1 memory space enable (mse) ? r/w. this bit controls access to the usb 2.0 memory space registers. 0 = disables this functionality. 1 = enables accesses to the usb 2.0 registers. the base address register (d29:f7, d26:f7:10h) for usb 2.0 should be pr ogrammed before this bit is set. 0 i/o space enable (iose) ? ro. hardwired to 0. http://www..net/ datasheet pdf - http://www..net/ ehci controller registers (d29:f7, d26:f7) 614 datasheet 17.1.4 pcists?pci status regist er (usb ehci?d29:f7, d26:f7) address offset: 06h ? 07h attribute: r/wc, ro default value: 0290h size: 16 bits note: for the writable bits, software must write a 1 to clear bits that are set. writing a 0 to the bit has no effect. bit description 15 detected parity error (dpe) ? r/wc. 0 = no parity error detected. 1 = this bit is set by the ich10 when a pari ty error is seen by the ehci controller, regardless of the setting of bit 6 or bit 8 in the command register or any other conditions. 14 signaled system error (sse) ? r/wc. 0 = no serr# signaled by ich10. 1 = this bit is set by the ich10 when it signals serr# (internally). the ser_en bit (bit 8 of the command register) must be 1 for this bit to be set. 13 received master abort (rma) ? r/wc. 0 = no master abort received by ehc on a memory access. 1 = this bit is set when ehc, as a master, receives a master abort status on a memory access. this is treated as a host error and halts the dma engines. this event can optionally generate an serr# by setting the serr# enable bit . 12 received target abort (rta) ? r/wc. 0 = no target abort received by ehc on memory access. 1 = this bit is set when ehc, as a master, re ceives a target abort status on a memory access. this is treated as a host error and halts the dma engines. this event can optionally generate an serr# by setting the serr# enable bit (d29:f7, d26:f7:04h, bit 8). 11 signaled target abort (sta) ? ro. this bit is used to indicate wh en the ehci function responds to a cycle with a target abort. there is no reason for this to happen, so this bit is hardwired to 0. 10:9 devsel# timing status (devt_sts) ? ro. this 2-bit field defines the timing for devsel# assertion. 8 master data parity error detected (dped) ? r/wc. 0 = no data parity error detected on usb2.0 read completion packet. 1 = this bit is set by the ich10 when a data parity error is detected on a usb 2.0 read completion packet on the internal interface to the ehci host controller and bit 6 of the command regist er is set to 1. 7 fast back to back capable (fb2bc) ? ro. hardwired to 1. 6 user definable features (u df) ? ro. hardwired to 0. 5 66 mhz capable (66 mhz _cap) ? ro. hardwired to 0. 4 capabilities list (cap _list) ? ro. hardwired to 1 indica ting that offset 34h contains a valid capabilities pointer. 3 interrupt status ? ro. this bit reflects the state of this function?s interrupt at the input of the enable/disable logic. 0 = this bit will be 0 when the interrupt is deasserted. 1 = this bit is a 1 when th e interrupt is asserted. the value reported in this bit is independen t of the value in the interrupt enable bit. 2:0 reserved http://www..net/ datasheet pdf - http://www..net/ datasheet 615 ehci controller registers (d29:f7, d26:f7) 17.1.5 rid?revision identification register (usb ehci?d29:f7, d26:f7) offset address: 08h attribute: ro default value: see bit description size: 8 bits 17.1.6 pi?programming interface register (usb ehci?d29:f7, d26:f7) address offset: 09h attribute: ro default value: 20h size: 8 bits 17.1.7 scc?sub class code register (usb ehci?d29:f7, d26:f7) address offset: 0ah attribute: ro default value: 03h size: 8 bits 17.1.8 bcc?base clas s code register (usb ehci?d29:f7, d26:f7) address offset: 0bh attribute: ro default value: 0ch size: 8 bits bit description 7:0 revision id ? ro. refer to the intel ? i/o controller hub (ich10) family specification update for the value of the revision id register bit description 7:0 programming interface ? ro. a value of 20h indicates that this usb 2.0 host controller conforms to the ehci specification. bit description 7:0 sub class code (scc) ? ro. 03h = universal serial bus host controller. bit description 7:0 base class code (bcc) ? ro. 0ch = serial bus controller. http://www..net/ datasheet pdf - http://www..net/ ehci controller registers (d29:f7, d26:f7) 616 datasheet 17.1.9 pmlt?primary master latency timer register (usb ehci?d29:f7, d26:f7) address offset: 0dh attribute: ro default value: 00h size: 8 bits 17.1.10 mem_base?memory ba se address register (usb ehci?d29:f7, d26:f7) address offset: 10h ? 13h attribute: r/w, ro default value: 00000000h size: 32 bits 17.1.11 svid?usb ehci subsys tem vendor id register (usb ehci?d29:f7, d26:f7) address offset: 2ch ? 2dh attribute: r/w default value: xxxxh size: 16 bits reset: none bit description 7:0 master latency timer count (mltc) ? ro. hardwired to 00h. because the ehci controller is internally implemented with arbitration on an interface (and not pci), it does not need a master latency timer. bit description 31:10 base address ? r/w. bits [31:10] correspond to memory address signals [31:10], respectively. this gives 1-kb of locatable memory space aligned to 1-kb boundaries. 9:4 reserved 3 prefetchable ? ro. hardwired to 0 indicating that this range should not be prefetched. 2:1 type ? ro. hardwired to 00b indicating th at this range can be mapped anywhere within 32-bit address space. 0 resource type indicator (rte) ? ro. hardwired to 0 indicating that the base address field in this regist er maps to memory space. bit description 15:0 subsystem vendor id (svid) ? r/w. this register, in combination with the usb 2.0 subsystem id register, enable s the operating system to distinguish each subsystem from the others. note: writes to this register are enable d when the wrt_rdonly bit (d29:f7, d26:f7:80h, bit 0) is set to 1. http://www..net/ datasheet pdf - http://www..net/ datasheet 617 ehci controller registers (d29:f7, d26:f7) 17.1.12 sid?usb ehci su bsystem id register (usb ehci?d29:f7, d26:f7) address offset: 2eh ? 2fh attribute: r/w default value: xxxxh size: 16 bits reset: none 17.1.13 cap_ptr?capabilit ies pointer register (usb ehci?d29:f7, d26:f7) address offset: 34h attribute: ro default value: 50h size: 8 bits 17.1.14 int_ln?interrupt line register (usb ehci?d29:f7, d26:f7) address offset: 3ch attribute: r/w default value: 00h size: 8 bits function level reset: no 17.1.15 int_pn?interrupt pin register (usb ehci?d29:f7, d26:f7) address offset: 3dh attribute: ro default value: see description size: 8 bits bit description 15:0 subsystem id (sid) ? r/w. bios sets the value in this register to identify the subsystem id. this re gister, in combination with the subsystem vendor id register, enables the operating system to distinguish each subsystem from other(s). note: writes to this register are enabled when the wrt_rdonly bit (d29:f7, d26:f7:80h, bit 0) is set to 1. bit description 7:0 capabilities pointer (cap_ptr) ? ro. this register points to the starting offset of the usb 2.0 capabilities ranges. bit description 7:0 interrupt line (int_ln) ? r/w. this data is not used by the intel ? ich10. it is used as a scratchpad register to communicate to software th e interrupt line that the interrupt pin is connected to. bit description 7:0 interrupt pin ? ro. this reflects the value of d29ip.eip (chipset config registers:offset 3108:bits 31:28) or d26ip.eip (chipset config registers:offset 3114:bits 31:28). note: bits 7:4 are always 0h http://www..net/ datasheet pdf - http://www..net/ ehci controller registers (d29:f7, d26:f7) 618 datasheet 17.1.16 pwr_capid?pci power management capability id register (usb ehci?d29:f7, d26:f7) address offset: 50h attribute: ro default value: 01h size: 8 bits 17.1.17 nxt_ptr1?next item pointer #1 register (usb ehci?d29:f7, d26:f7) address offset: 51h attribute: r/w default value: 58h size: 8 bits bit description 7:0 power management capability id ? ro. a value of 01h indicates that this is a pci power management ca pabilities field. bit description 7:0 next item pointer 1 value ? r/w (special). this regi ster defaults to 58h, which indicates that the next capa bility registers begin at co nfiguration offset 58h. this register is writable when the wrt_rdonly bit (d29:f7, d26:f7:80h, bit 0) is set. this allows bios to effectively hide the debug port capability registers, if necessary. this register should only be written during sy stem initialization before the plug-and-play software has enabled any master-initiated tr affic. only values of 58h (debug port visible) and 00h (debug port invisible) are expected to be programmed in this register. note: register not reset by d3-to-d0 warm reset. http://www..net/ datasheet pdf - http://www..net/ datasheet 619 ehci controller registers (d29:f7, d26:f7) 17.1.18 pwr_cap?power manageme nt capabilities register (usb ehci?d29:f7, d26:f7) address offset: 52h ? 53h attribute: r/w, ro default value: c9c2h size: 16 bits notes: 1. normally, this register is read-only to re port capabilities to the power management software. to report different power management capabilities, dependin g on the system in which the ich10 is used, bits 15:11 and 8:6 in this register are writable when the wrt_rdonly bit (d29:f7, d26:f7:80h, bit 0) is set. the value written to this register does not affect the hardware other than changi ng the value returned during a read. 2. reset: core well, but not d3-to-d0 warm reset. bit description 15:11 pme support (pme_sup) ? r/w. this 5-bit field indicates the power states in which the function may assert pme#. the intel ? ich10 ehc does not support the d1 or d2 states. for all other states, the ich10 ehc is capable of generating pme#. software should never need to modify this field. 10 d2 support (d2_sup) ? ro. 0 = d2 state is not supported 9 d1 support (d1_sup) ? ro. 0 = d1 state is not supported 8:6 auxiliary current (aux_cur) ? r/w . the ich10 ehc reports 375 ma maximum suspend well current re quired when in the d3 cold state. 5 device specific initialization (dsi )? ro. the ich10 reports 0, indicating that no device-specific initialization is required. 4 reserved 3 pme clock (pme_clk) ? ro. the ich10 reports 0, indicati ng that no pci clock is required to generate pme#. 2:0 version (ver) ? ro. the ich10 reports 010b, indicati ng that it complies with revision 1.1 of the pci power management specification. http://www..net/ datasheet pdf - http://www..net/ ehci controller registers (d29:f7, d26:f7) 620 datasheet 17.1.19 pwr_cntl_sts?power management control/ status register (usb ehci?d29:f7, d26:f7) address offset: 54h ? 55h attribute: r/w, r/wc, ro default value: 0000h size: 16 bits function level reset: no (bits 8 and 15 only) note: reset (bits 15, 8): suspend well, and not d3 -to-d0 warm reset no r core well reset. bit description 15 pme status ? r/wc. 0 = writing a 1 to this bit will clear it and cause the internal pme to deassert (if enabled). 1 = this bit is set when the ich10 ehc wo uld normally assert the pme# signal independent of the state of the pme_en bit. note: this bit must be explicitly cleared by the operating system each time the operating system is loaded. this bit is not reset by function level reset. 14:13 data scale ? ro. hardwired to 00b indicating it does not support the associated data register. 12:9 data select ? ro. hardwired to 0000b indicating it does not support the associated data register. 8 pme enable ? r/w. 0 = disable. 1 = enables intel ? ich10 ehc to generate an internal pme signal when pme_status is 1. note: this bit must be explicitly cleared by the operating system each time it is initially loaded. this bit is not reset by function level reset. 7:2 reserved 1:0 power state ? r/w. this 2-bit field is used both to determine the cu rrent power state of ehc function and to set a new power state. the definition of the field values are: 00 = d0 state 11 = d3 hot state if software attempts to write a value of 10b or 01b in to this field, the write operation must complete normally; however, the data is discarded and no state change occurs. when in the d3 hot state, the ich10 must not accept accesses to the ehc memory range; but the configuration space must still be accessible. when not in the d0 state, the generation of the interrupt output is bloc ked. specifically, the pirqh is not asserted by the ich10 when not in the d0 state. when software changes this value from the d3 hot state to the d0 state, an internal warm (soft) reset is gene rated, and software must re-initialize the function. http://www..net/ datasheet pdf - http://www..net/ datasheet 621 ehci controller registers (d29:f7, d26:f7) 17.1.20 debug_capid?debug port capability id register (usb ehci?d29:f7, d26:f7) address offset: 58h attribute: ro default value: 0ah size: 8 bits 17.1.21 nxt_ptr2?next item pointer #2 register (usb ehci?d29:f7, d26:f7) address offset: 59h attribute: ro default value: 98h size: 8 bits function level reset: no 17.1.22 debug_base?debug port base offset register (usb ehci?d29:f7, d26:f7) address offset: 5ah ? 5bh attribute: ro default value: 20a0h size: 16 bits 17.1.23 usb_relnum?usb re lease number register (usb ehci?d29:f7, d26:f7) address offset: 60h attribute: ro default value: 20h size: 8 bits bit description 7:0 debug port capability id ? ro. hardwired to 0ah indicating that this is the start of a debug port capability structure. bit description 7:0 next item pointer 2 capability ? ro. this register points to the next capability in the function level reset capability structure. bit description 15:13 bar number ? ro. hardwired to 001b to indicate the memory bar begins at offset 10h in the ehci configuration space. 12:0 debug port offset ? ro. hardwired to 0a0h to indica te that the debug port registers begin at offset a0h in the ehci memory range. bit description 7:0 usb release number ? ro. a value of 20h indicates that this controller follows universal serial bus (usb) sp ecification, revision 2.0 . http://www..net/ datasheet pdf - http://www..net/ ehci controller registers (d29:f7, d26:f7) 622 datasheet 17.1.24 fl_adj?frame length adjustment register (usb ehci?d29:f7, d26:f7) address offset: 61h attribute: r/w default value: 20h size: 8 bits function level reset: no this feature is used to adjust any offset from the clock source that generates the clock that drives the sof counter. when a new value is written into these six bits, the length of the frame is adjusted. its initial programmed value is system dependent based on the accuracy of hardware usb clock and is initialized by system bios. this register should only be modified when the hcha lted bit (d29:f7, d26:f7:caplength + 24h, bit 12) in the usb2.0_sts register is a 1. changing value of this register while the host controller is operating yields undefined resu lts. it should not be reprogrammed by usb system software unless the default or bios programmed values are incorrect, or the system is restoring the register while returning from a suspended state. these bits in suspend well and not reset by a d3-to-d0 warm rest or a core well reset. bit description 7:6 reserved ? ro. these bits are reserved for future use and sh ould read as 00b. 5:0 frame length timing value ? r/w. each decimal value change to this register corresponds to 16 high-speed bit times. th e sof cycle time (number of sof counter clock periods to generate a sof micro-frame length) is equal to 59488 + value in this field. the default value is decimal 32 (20h), which gives a sof cycle time of 60000. frame length (# 480 mhz clocks) (decimal) frame length timing value (this register) (decimal) 59488 0 59504 1 59520 2 ?? 59984 31 60000 32 ?? 60480 62 http://www..net/ datasheet pdf - http://www..net/ datasheet 623 ehci controller registers (d29:f7, d26:f7) 17.1.25 pwake_cap?port wake capability register (usb ehci?d29:f7, d26:f7) address offset: 62 ? 63h attribute: r/w default value: 01ffh size: 16 bits function level reset: no this register is in the suspend power well. the intended use of this register is to establish a policy about which ports are to be used for wake events. bit positions 1? 8(d29) or 1?6(d26) in the mask correspon d to a physical port implemented on the current ehci controller. a 1 in a bit position indicates that a device connected below the port can be enabled as a wake-up device and the port may be enabled for disconnect/ connect or overcurrent events as wake-up events. this is an information-only mask register. the bits in this register do not affect the actual operation of the ehci host controller. the system-specific policy can be established by bios initializing this register to a system-specific value. system software uses the information in this register when enabling devices and ports for remote wake-up. these bits are not reset by a d3-to-d0 warm rest or a core well reset. bit description 15:9 (d29) 15:7 (d26) reserved. 8:1 (d29) 6:1 (d26) port wake up capability mask ? r/w. bit positions 1 through 8 (device 29) or 1 through 6(device 26) correspond to a physical port implemented on this host controller. for example, bit position 1 corresponds to port 1, bit position 2 corresponds to port 2, etc. 0 port wake implemented ? r/w. a 1 in this bit indicates that this register is implemented to software. http://www..net/ datasheet pdf - http://www..net/ ehci controller registers (d29:f7, d26:f7) 624 datasheet 17.1.26 leg_ext_cap?usb ehci legacy support extended capability register (usb ehci?d29:f7, d26:f7) address offset: 68 ? 6bh attribute: r/w, ro default value: 00000001h size: 32 bits power well: suspend function level reset: no note: these bits are not reset by a d3-to- d0 warm rest or a core well reset. 17.1.27 leg_ext_cs?usb ehci legacy support extended control / status register (usb ehci?d29:f7, d26:f7) address offset: 6c ? 6fh attribute: r/w, r/wc, ro default value: 00000000h size: 32 bits power well: suspend function level reset: no note: these bits are not reset by a d3-to- d0 warm rest or a core well reset. bit description 31:25 reserved ? ro. hardwired to 00h 24 hc os owned semaphore ? r/w. system software sets this bit to request ownership of the ehci controller. ownership is obtained when this bit reads as 1 and the hc bios owned semaphore bit reads as clear. 23:17 reserved ? ro. hardwired to 00h 16 hc bios owned semaphore ? r/w. the bios sets this bit to establish ownership of the ehci controller. system bios will clea r this bit in response to a request for ownership of the ehci contro ller by system software. 15:8 next ehci capability pointer ? ro. hardwired to 00h to indicate that there are no ehci extended capability st ructures in this device. 7:0 capability id ? ro. hardwired to 01h to indicate th at this ehci extended capability is the legacy support capability. bit description 31 smi on bar ? r/wc. software clears this bit by writing a 1 to it. 0 = base address regist er (bar) not written. 1 = this bit is set to 1 when the base address register (bar) is written. 30 smi on pci command ? r/wc. software clears this bit by writing a 1 to it. 0 = pci command (pcicmd) register not written. 1 = this bit is set to 1 when the pci command (pcicmd) re gister is written. 29 smi on os ownership change ? r/wc. software clears this bit by writing a 1 to it. 0 = no hc os owned semaphore bit change. 1 = this bit is set to 1 when the hc os owned semaphore bit in the leg_ext_cap register (d29:f7, d26:f7:68h, bit 24) transitions from 1 to 0 or 0 to 1. 28:22 reserved. http://www..net/ datasheet pdf - http://www..net/ datasheet 625 ehci controller registers (d29:f7, d26:f7) 21 smi on async advance ? ro. this bit is a shadow bit of the interrupt on async advance bit (d29:f7, d26:f7:caplength + 24h, bit 5) in the usb2.0_sts register. note: to clear this bit system software must write a 1 to the interrupt on async advance bit in the usb2.0_sts register. 20 smi on host system error ? ro. this bit is a shadow bit of host system error bit in the usb2.0_sts register (d29:f7, d26:f7:caplength + 24h, bit 4). note: to clear this bit system so ftware must write a 1 to th e host system error bit in the usb2.0_sts register. 19 smi on frame list rollover ? ro. this bit is a shadow bit of frame list rollover bit (d29:f7, d26:f7:caplength + 24h, bit 3) in the usb2.0_sts register. note: to clear this bit system software must write a 1 to the frame list rollover bit in the usb2.0_sts register. 18 smi on port change detect ? ro. this bit is a shadow bi t of port change detect bit (d29:f7, d26:f7:caplength + 24h, bit 2) in the usb2.0_sts register. note: to clear this bit system software must wr ite a 1 to the port change detect bit in the usb2.0_sts register. 17 smi on usb error ? ro. this bit is a shadow bit of usb error interrupt (usberrint) bit (d29:f7, d26:f7:caplength + 24h, bit 1) in the usb2.0_sts register. note: to clear this bit system software must wr ite a 1 to the usb error interrupt bit in the usb2.0_sts register. 16 smi on usb complete ? ro. this bit is a shadow bit of usb interrupt (usbint) bit (d29:f7, d26:f7:caplength + 24h, bit 0) in the usb2.0_sts register. note: to clear this bit system so ftware must write a 1 to th e usb interrupt bit in the usb2.0_sts register. 15 smi on bar enable ? r/w. 0 = disable. 1 = enable. when this bit is 1 and smi on bar (d29:f7, d26:f7:6ch, bit 31) is 1, then the host controller will issue an smi. 14 smi on pci command enable ? r/w. 0 = disable. 1 = enable. when this bit is 1 and smi on pci command (d29:f7, d26:f7:6ch, bit 30) is 1, then the host cont roller will issue an smi. 13 smi on os ownership enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1 and the os ownership change bit (d29:f7, d26:f7:6ch, bit 29) is 1, the host controller will issue an smi. 12:6 reserved. 5 smi on async advance enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1, and the smi on as ync advance bit (d29:f7, d26:f7:6ch, bit 21) is a 1, the host co ntroller will issue an smi immediately. 4 smi on host system error enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1, and the smi on host system error (d29:f7, d26:f7:6ch, bit 20) is a 1, the ho st controller will issue an smi. bit description http://www..net/ datasheet pdf - http://www..net/ ehci controller registers (d29:f7, d26:f7) 626 datasheet 17.1.28 special_smi?intel spec ific usb 2.0 smi register (usb ehci?d29:f7, d26:f7) address offset: 70h ? 73h attribute: r/w, r/wc default value: 00000000h size: 32 bits power well: suspend function level reset: no note: these bits are not reset by a d3-to- d0 warm rest or a core well reset. 3 smi on frame list rollover enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1, and th e smi on frame list rollover bit (d29:f7, d26:f7:6ch, bit 19) is a 1, the ho st controller will issue an smi. 2 smi on port change enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1, and th e smi on port change detect bit (d29:f7, d26:f7:6ch, bit 18) is a 1, the ho st controller will issue an smi. 1 smi on usb error enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1, and the smi on usb error bit (d29:f7, d26:f7:6ch, bit 17) is a 1, the host controll er will issue an smi immediately. 0 smi on usb complete enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1, an d the smi on usb complete bit (d29:f7, d26:f7:6ch, bit 16) is a 1, the host co ntroller will issue an smi immediately. bit description bit description 31:30 (d29) 31:28 (d26) reserved. 29:22 (d29) 27:22 (d26) smi on portowner ? r/wc. software clears these bits by writing a 1 to it. 0 = no port owner bit change. 1 = bits 29:22, 27:22 correspond to the port owner bits for ports 1 (22) through 6 (27) or 8 (29). these bits are set to 1 when the associated port owner bits transition from 0 to 1 or 1 to 0. 21 smi on pmcsr ? r/wc. software clears these bits by writing a 1 to it. 0 = power state bits not modified. 1 = software modified the power state bits in the power management control/status (pmcsr) register (d29:f7, d26:f7:54h). 20 smi on async ? r/wc. software clears these bits by writing a 1 to it. 0 = no async schedule enable bit change 1 = async schedule enable bit transitioned from 1 to 0 or 0 to 1. 19 smi on periodic ? r/wc. software clears this bit by writing a 1 it. 0 = no periodic schedule enable bit change. 1 = periodic schedule enable bit transitions from 1 to 0 or 0 to 1. http://www..net/ datasheet pdf - http://www..net/ datasheet 627 ehci controller registers (d29:f7, d26:f7) 18 smi on cf ? r/wc. software clears this bit by writing a 1 it. 0 = no configure flag (cf) change. 1 = configure flag (cf) transitions from 1 to 0 or 0 to 1. 17 smi on hchalted ? r/wc. software clears this bit by writing a 1 it. 0 = hchalted did not transition to 1 (as a re sult of the run/stop bit being cleared). 1 = hchalted transitions to 1 (as a result of the run/stop bit being cleared). 16 smi on hcreset ? r/wc. software clears th is bit by writing a 1 it. 0 = hcreset did not transitioned to 1. 1 = hcreset transitioned to 1. 15:14 reserved. 13:6 smi on portowner enable ? r/w. 0 = disable. 1 = enable. when any of these bits are 1 an d the corresponding smi on portowner bits are 1, then the host controller will issu e an smi. unused port s should have their corresponding bits cleared. 5 smi on pmscr enable ? r/w. 0 = disable. 1 = enable. when this bit is 1 and smi on pm scr is 1, then the host controller will issue an smi. 4 smi on async enable ? r/w. 0 = disable. 1 = enable. when this bit is 1 and smi on async is 1, then the host controller will issue an smi 3 smi on periodic enable ? r/w. 0 = disable. 1 = enable. when this bit is 1 and smi on peri odic is 1, then the host controller will issue an smi. 2 smi on cf enable ? r/w. 0 = disable. 1 = enable. when this bit is 1 and smi on cf is 1, then the host controller will issue an smi. 1 smi on hchalted enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1 and smi on hchalted is 1, then the host controller will issue an smi. 0 smi on hcreset enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1 and smi on hcreset is 1, then host controller will issue an smi. bit description http://www..net/ datasheet pdf - http://www..net/ ehci controller registers (d29:f7, d26:f7) 628 datasheet 17.1.29 access_cntl?access control register (usb ehci?d29:f7, d26:f7) address offset: 80h attribute: r/w default value: 00h size: 8 bits function level reset: no 17.1.30 ehciir1?ehci init ialization register 1 (usb ehci?d29:f7, d26:f7) address offset: 84h attribute: r/w default value: 01h size: 8 bits 17.1.31 flr_cid?function le vel reset capability id (usb ehci?d29:f7, d26:f7) address offset: 98h attribute: ro default value: 09h size: 8 bits function level reset: no bit description 7:1 reserved 0 wrt_rdonly ? r/w. when set to 1, this bit enables a select group of normally read- only registers in the ehc function to be writ ten by software. registers that may only be written when this mode is entered are noted in the summary tables and detailed description as ?read/write-special?. th e registers fall into two categories: 1. system-configure d parameters, and 2. status bits bit description 7:5 reserved 4 pre-fetch based pause disable ? r/w. 0 = pre-fetch based pause is enabled. 1 = pre-fetch based pause is disabled. 3:0 reserved bit description 7:0 capability id ? r0. 13h = if flrcssel = 0 09h (vendor specific capability) = if flrcssel = 1 http://www..net/ datasheet pdf - http://www..net/ datasheet 629 ehci controller registers (d29:f7, d26:f7) 17.1.32 flr_next?function level re set next capability pointer (usb ehci?d29:f7, d26:f7) address offset: 99h attribute: ro default value: 00h size: 8 bits function level reset: no 17.1.33 flr_clv?function level reset capability length and version (usb ehci?d29:f7, d26:f7) address offset: 9ah-9bh attribute: r/wo, ro default value: 2006h size: 16 bits function level reset: no when flrcssel = 0, this register is defined as follows: when flrcssel = 1, this register is defined as follows: bit description 7:0 a value of 00h in this register indi cates this is the last capability field. bit description 15:10 reserved. 9 flr capability ? r/wo. 1 = support for function level reset (flr). 8 txp capability ? r/wo. 1 = support for transactions pending (txp) bit. txp must be supported if flr is supported. 7:0 capability length ? ro. this field indicates the # of bytes of this vendor specific capability as required by the pci specific ation. it has the value of 06h for the flr capability. bit description 15:12 vendor specific capability id ? ro. a value of 2h in this field identifies this capability as function level reset. 11:8 capability version ? ro. this field indicates the version of the flr capability. 7:0 capability length ? ro. this field indicates the # of bytes of this vendor specific capability as required by the pci specific ation. it has the value of 06h for the flr capability. http://www..net/ datasheet pdf - http://www..net/ ehci controller registers (d29:f7, d26:f7) 630 datasheet 17.1.34 flr_ctrl?function le vel reset control register (usb ehci?d29:f7, d26:f7) address offset: 9ch attribute: r/w default value: 00h size: 8 bits function level reset: no 17.1.35 flr_sts?function le vel reset status register (usb ehci?d29:f7, d26:f7) address offset: 9dh attribute: ro default value: 00h size: 8 bits function level reset: no 17.1.36 ehciir2?ehci init ialization register 2 (usb ehci?d29:f7, d26:f7) address offset: fch attribute: r/w default value: 20001706h size: 32 bits bit description 7:1 reserved 0 initiate flr ? r/w. this bit is used to initiate flr transition. a write of ?1? initiates flr transition. since hardware must not respond to any cycles until flr completion, the value read by software from this bit is always ?0?. bit description 7:1 reserved 0 transactions pending (txp) ? ro. 0 = completions for all non-posted requests have been received. 1 = controller has issued non-posted requests which have no bee completed. bit description 31:30 reserved 29 ehciir2 field 2 ? r/w. bios must set this bit 28:18 reserved 17 ehciir2 field 1 ? r/w. bios must set this bit 16:4 reserved 3:2 ehciir2 field 3 ? r/w. bios must set this field to 10b 1:0 reserved http://www..net/ datasheet pdf - http://www..net/ datasheet 631 ehci controller registers (d29:f7, d26:f7) 17.2 memory-mapped i/o registers the ehci memory-mapped i/o space is composed of two sets of registers: capability registers and operational registers. note: the ich10 ehci controller will not accept memory transactions (neither reads nor writes) as a target that are locked transactions. the locked transactions should not be forwarded to pci as the address space is known to be allocated to usb. note: when the ehci function is in the d3 pci power state, accesses to the usb 2.0 memory range are ignored and result a master abort. similarly, if the memory space enable (mse) bit (d29:f7, d26:f7:04h, bit 1) is not set in the command register in configuration space, the memory range will not be decoded by the ich10 enhanced host controller (ehc). if the mse bit is not se t, then the ich10 must default to allowing any memory accesses for the range specified in the bar to go to pci. this is because the range may not be valid and, therefore, the cycle must be made available to any other targets that may be currently using that range. 17.2.1 host controller capability registers these registers specify the limits, restrictio ns and capabilities of the host controller implementation. within the host controller capability registers, only the structural parameters register is writable. these re gisters are implemented in the suspend well and is only reset by the standard suspend- well hardware reset, not by hcreset or the d3-to-d0 reset. note: note that the ehci controller does not support as a target memory transactions that are locked transactions. attempting to a ccess the ehci controller memory-mapped i/o space using locked memory transactions will result in undefined behavior. note: note that when the usb2 function is in th e d3 pci power state, accesses to the usb2 memory range are ignored and will result in a master abort similarly, if the memory space enable (mse) bit is not set in the co mmand register in configuration space, the memory range will not be decoded by the e nhanced host controller (ehc). if the mse bit is not set, then the ehc will not claim any memory accesses for the range specified in the bar. note: ?read/write special? means that the register is normally read-only, but may be written when the wrt_rdonly bit is set. because these registers are expected to be programmed by bios during initialization, their contents must not get modified by hcreset or d3-to- d0 internal reset. table 17-2. enhanced host co ntroller capability registers mem_base + offset mnemonic register default type 00h caplength capabilities registers length 20h ro 02h?03h hciversion host controller interface version number 0100h ro 04h?07h hcsparams host controller structural parameters 00103206h (d29:f7) 00102205 (d26:f7) r/w (special), ro 08h?0bh hccparams host controller capability parameters 00006871h ro http://www..net/ datasheet pdf - http://www..net/ ehci controller registers (d29:f7, d26:f7) 632 datasheet 17.2.1.1 caplength? capability registers length register offset: mem_base + 00h attribute: ro default value: 20h size: 8 bits 17.2.1.2 hciversion?host contro ller interface version number register offset: mem_base + 02h ? 03h attribute: ro default value: 0100h size: 16 bits bit description 7:0 capability register length value ? ro. this register is used as an offset to add to the memory base register (d29:f7, d26:f7:10h) to find the beginning of the operational register space. this field is ha rdwired to 20h indicating that the operation registers begin at offset 20h. bit description 15:0 host controller interface version number ? ro. this is a two-byte register containing a bcd encoding of the version number of interface that this ho st controller interface conforms. http://www..net/ datasheet pdf - http://www..net/ datasheet 633 ehci controller registers (d29:f7, d26:f7) 17.2.1.3 hcsparams?host controller structural parameters offset: mem_base + 04h ? 07h attribute: r/w, ro default value: 00103206h (d29:f7) size: 32 bits 00103206h (d26:f7) function level reset: no note: this register is reset by a suspend well reset and not a d3-to-d0 reset or hcreset. note: this register is writable when the wrt_rdonly bit is set. bit description 31:24 reserved. 23:20 debug port number (dp_n) ? ro. hardwired to 1h indicating that the debug port is on the lowest numbere d port on the ehci. 19:16 reserved 15:12 number of companion controllers (n_cc) ? r/w. this field indicates the number of companion controllers associated with this usb ehci host controller. a 0 in this field indicates there are no comp anion host controllers. port-ownership hand- off is not supported. only hi gh-speed devices are supported on the host controller root ports. a value of 1 or more in this field indicates there are companion usb uhci host controller(s). port-ownership hand-offs are supported. high, full- and low-speed devices are supported on the host controller root ports. the ich10 allows the default value of 3h (d29 ) or 3h (d26) to be over-written by bios. when removing classic controllers, they mu st be disabled in the following order: function 3, function 2, function 1, and function 0, which correspond to ports 11:10, 5:4, 3:2, and 1:0, respectively for device 29. for device 26 the following order is function 2, function 1 then function 0, wh ich correspond to ports 11:10, 9:8 and 7:6, respectively. 11:8 number of ports per companion controller (n_pcc) ? ro. hardwired to 2h. this field indicates the number of po rts supported per companion host controller. it is used to indicate the port routing conf iguration to system software. 7:4 reserved. these bits are reserved and default to 0. 3:0 n_ports ? r/w. this field specifies the number of physical downstream ports implemented on this host controller. the valu e of this field determines how many port registers are addressable in the operational register space. valid values are in the range of 1h to fh. the ich10 reports 6h for d29 and 6h for d26 by default. however, software may write a value less than the default for some platfo rm configurations. a 0 in this field is undefined. http://www..net/ datasheet pdf - http://www..net/ ehci controller registers (d29:f7, d26:f7) 634 datasheet 17.2.1.4 hccparams?host cont roller capability parameters register offset: mem_base + 08h ? 0bh attribute: ro default value: 00006871h size: 32 bits bit description 31:18 reserved 17 asynchronous schedule update capability (asuc) ? r/w. there is no functionality associated with this bit. 16 periodic schedule update capability (psuc) ? ro. this field is hardwired to 0b to indicate that the ehc hardware supports the pe riodic schedule update event flag in the usb2.0_cmd register. 15:8 ehci extended capabili ties pointer (eecp) ? ro. this field is hardwired to 68h, indicating that the ehci capa bilities list exists and begins at offset 68h in the pci configuration space. 7:4 isochronous scheduling threshold ? ro. this field indicates, relative to the current position of the executing host contro ller, where software can reliably update the isochronous schedule. wh en bit 7 is 0, the value of the least significant 3 bits indicates the number of micro-frames a host controller hold a set of isochr onous data structures (one or more) before fl ushing the state. when bit 7 is a 1, then host software assumes the host controller may cache an isochronous data structure for an entire frame. refer to the ehci specification for details on how software uses this information for scheduling isochronous transfers. this field is hardwired to 7h. 3 reserved. 2 asynchronous schedule park capability ? ro. this bit is hardwired to 0 indicating that the host controller does no t support this optional feature 1 programmable frame list flag ? ro. 0 = system software must use a frame list length of 1024 elements with this host controller. the usb2.0_cmd register (d 29:f7, d26:f7:caplength + 20h, bits 3:2) frame list size field is a read-only regist er and must be set to 0. 1 = system software can specify and use a sm aller frame list and configure the host controller via the us b2.0_cmd register frame list size field. the frame list must always be aligned on a 4k page boundary . this requirement en sures that the frame list is always physically contiguous. 0 64-bit addressing capability ? ro. this field documents the addressing range capability of this implementation. the value of this field determin es whether software should use the 32-bit or 64-bit data structures . values for this field have the following interpretation: 0 = data structures using 32- bit address memory pointers 1 = data structures using 64-bit address memory pointers this bit is hardwired to 1. note: ich10 supports 64 bit addressing only. http://www..net/ datasheet pdf - http://www..net/ datasheet 635 ehci controller registers (d29:f7, d26:f7) 17.2.2 host controller operational registers this section defines the enhanced host controller operational registers. these registers are located after the capabilities registers. the operational register base must be dword-aligned and is calculated by adding the value in the first capabilities register (caplength) to the base address of the enhanced host controller register address space (mem_base). since caplength is always 20h, table 17-3 already accounts for this offset. all registers are 32 bits in length. note: software must read and write these registers using only dword accesses.these registers are divided into two sets. the fi rst set at offsets mem_base + 00:3bh are implemented in the core powe r well. unless otherwise noted, the core well registers are reset by the assertion of any of the following: ? core well hardware reset ? hcreset ? d3-to-d0 reset table 17-3. enhanced host controlle r operational register address map mem_bas e + offset mnemonic register name default special notes type 20h?23h usb2.0_cmd usb 2.0 command 00080000h r/w, ro 24h?27h usb2.0_sts usb 2.0 status 00001000h r/wc, ro 28h?2bh usb2.0_intr usb 2.0 interrupt enable 00000000h r/w 2ch?2fh frindex usb 2.0 frame index 00000000h r/w, 30h?33h ctrldssegment control data structure segment 00000000h r/w, ro 34h?37h perodiclistbase period frame list base address 00000000h r/w 38h?3bh asynclistaddr current asynchronous list address 00000000h r/w 3ch?5fh ? reserved 0h ro 60h?63h configflag configure flag 00000000h suspend r/w 64h?67h port0sc port 0 status and control 00003000h suspend r/w, r/wc, ro 68h?6bh port1sc port 1 status and control 00003000h suspend r/w, r/wc, ro 6ch?6fh port2sc port 2 status and control 00003000h suspend r/w, r/wc, ro 70h?73h port3sc port 3 status and control 00003000h suspend r/w, r/wc, ro 74h?77h port4sc port 4 status and control 00003000h suspend r/w, r/wc, ro 78h?7bh port5sc port 5 status and control 00003000h suspend r/w, r/wc, ro 74h?77h (d29 only) port6sc port 6 status and control 00003000h suspend r/w, r/wc, ro 78h?7bh (d29 only) port7sc port 7 status and control 00003000h suspend r/w, r/wc, ro 7ch?9fh ? reserved undefined ro a0h?b3h ? debug port registers undefined see register description b4h?3ffh ? reserved undefined ro http://www..net/ datasheet pdf - http://www..net/ ehci controller registers (d29:f7, d26:f7) 636 datasheet the second set at offsets mem_base + 60h to the end of the implemented register space are implemented in the suspend po wer well. unless otherwise noted, the suspend well registers are reset by the assertion of either of the following: ? suspend well hardware reset ? hcreset 17.2.2.1 usb2.0_cmd?usb 2.0 command register offset: mem_base + 20?23h attribute: r/w, ro default value: 00080000h size: 32 bits bit description 31:24 reserved. 23:16 interrupt threshold control ? r/w. system software uses this field to select the maximum rate at which the host controller wi ll issue interrupts. the only valid values are defined below. if software writes an in valid value to this re gister, the results are undefined. 15:14 reserved. 13 asynch schedule update (asc) ? r/w. there is no function ality associated with this bit. 12 periodic schedule prefetch enable ? r/w. this bit is used by software to enable the host controller to prefetch the periodic schedule even in c0. 0 = prefetch based pause enabled only when not in c0. 1 = prefetch based pause enable in c0. once software has written a 1b to this bit to enable periodic schedule prefetching, it must disable prefec thing by writing a 0b to this bit whenever periodic schedule updates are about to begin. software should contin ue to dynamically disa ble and re-e nable the prefetcher surrounding any updates to the periodic scheduler (i.e. until the host controller has been reset via a hcreset). 11:8 unimplemented asynchronous park mode bits ? ro. hardwired to 000b indicating the host controller does not su pport this optional feature. 7 light host controller reset ? ro. hardwired to 0. the ich10 does not implement this optional reset. value maximum interrupt interval 00h reserved 01h 1 micro-frame 02h 2 micro-frames 04h 4 micro-frames 08h 8 micro-frames (default, equates to 1 ms) 10h 16 micro-frames (2 ms) 20h 32 micro-frames (4 ms) 40h 64 micro-frames (8 ms) http://www..net/ datasheet pdf - http://www..net/ datasheet 637 ehci controller registers (d29:f7, d26:f7) 6 interrupt on async advance doorbell ? r/w. this bit is used as a doorbell by software to tell the host controller to is sue an interrupt the ne xt time it advances asynchronous schedule. 0 = the host controller sets this bit to a 0 after it has set the interrupt on async advance status bit (d29:f7, d26:f7:caplength + 24h, bit 5) in the usb2.0_sts register to a 1. 1 = software must write a 1 to this bit to ri ng the doorbell. when the host controller has evicted all appropriate cached schedule state, it sets the interrupt on async advance status bit in the usb2.0_sts register. if the interrupt on async advance enable bit in the usb2.0_intr register (d29:f7, d26:f7:caplength + 28h, bit 5) is a 1 then the host controller will as sert an interrupt at the next interrupt threshold. see the ehci specif ication for operational details. note: software should not write a 1 to this bit when the asynchronous schedule is inactive. doing so will yield undefined results. 5 asynchronous schedule enable ? r/w. this bit controls whether the host controller skips processing the asynchronous schedule. 0 = do not process the asynchronous schedule 1 = use the asynclistaddr register to access the asynchronous schedule. 4 periodic schedule enable ? r/w. this bit controls whet her the host controller skips processing the periodic schedule. 0 = do not process the periodic schedule 1 = use the periodiclistbase register to access the periodic schedule. 3:2 frame list size ? ro. the ich10 hardwires this fiel d to 00b because it only supports the 1024-element frame list size. 1 host controller reset (hcreset) ? r/w. this control bit used by software to reset the host controller. the effects of this on root hub registers are similar to a chip hardware reset (i.e., rsmrst# assertio n and pwrok deassertion on the ich10). when software writes a 1 to th is bit, the host controller re sets its internal pipelines, timers, counters, state machines, etc. to their initial value. any transaction currently in progress on usb is immediat ely terminated. a usb reset is not driven on downstream ports. note: pci configuration registers and host controller capability registers are not effected by this reset. all operational registers, including port registers and port state machines are set to their initial values. port ownership reverts to the companion host controller(s), with the side effects described in the ehci spec. softwa re must re-initialize the host controller in order to return the host contro ller to an operational state. this bit is set to 0 by the host controller when the reset process is complete. software cannot terminate the reset process earl y by writing a 0 to this register. software should not set this bit to a 1 when the hchalted bit (d29:f7, d26:f7:caplength + 24h, bit 12) in the usb2.0_sts register is a 0. attempting to reset an actively running host controller will result in undefined behavior. this reset me be used to leave eh ci port test modes. bit description http://www..net/ datasheet pdf - http://www..net/ ehci controller registers (d29:f7, d26:f7) 638 datasheet note: the command register indicates the command to be executed by the serial bus host controller. writing to the register causes a command to be executed. 0 run/stop (rs) ? r/w. 0 = stop (default) 1 = run. when set to a 1, the host controller proceeds with execution of the schedule. the host controller continues execution as lo ng as this bit is set. when this bit is set to 0, the host controller completes the current transaction on the usb and then halts. the hchalted bit in the usb2.0_s ts register indicates when the host controller has finished the transaction and has entered the stopped state. software should not write a 1 to this field un less the host controller is in the halted state (i.e., hchalted in th e usbsts register is a 1). the halted bit is cleared immediately when the run bit is set. the following table explains how the different combinations of run and halted should be interpreted: memory read cycles initiated by the ehc that receive any status ot her than successful will result in this bit being cleared. bit description run/stop halted interpretation 0b 0b in the process of halting 0b 1b halted 1b 0b running 1b 1b invalid - the hchalted bit clears immediately http://www..net/ datasheet pdf - http://www..net/ datasheet 639 ehci controller registers (d29:f7, d26:f7) 17.2.2.2 usb2.0_sts?usb 2.0 status register offset: mem_base + 24h?27h attribute: r/wc, ro default value: 00001000h size: 32 bits this register indicates pending interrupts and various states of the host controller. the status resulting from a transaction on the serial bus is not indicated in this register. see the interrupts description in section 4 of the ehci specification for additional information concerning usb 2.0 interrupt conditions. note: for the writable bits, software must write a 1 to clear bits that are set. writing a 0 has no effect. bit description 31:16 reserved. 15 asynchronous schedule status ? ro. this bit reports the cu rrent real status of the asynchronous schedule. 0 = status of the asynchronous schedule is disabled. (default) 1 = status of the asynchronous schedule is enabled. note: the host controller is not required to immediately disable or enable the asynchronous schedule when software transitions the asynchronous schedule enable bit (d29:f7, d26:f7:caplength + 20h, bit 5) in the usb2.0_cmd register. when this bit and the asynchronous schedule enable bit are the same value, the asynchronous schedule is either enabled (1) or disabled (0). 14 periodic schedule status ? ro. this bit reports the current re al status of the periodic schedule. 0 = status of the periodic sche dule is disabled. (default) 1 = status of the periodic schedule is enabled. note: the host controller is not required to immediately disable or enable the periodic schedule when softwa re transitions the periodic schedule enable bit (d29:f7, d26:f7:caplength + 20h, bit 4) in the us b2.0_cmd register. when this bit and the periodic schedule enable bit are the same value, the periodic schedule is either enabled (1) or disabled (0). 13 reclamation ? ro. this read-only status bit is used to detect an empty asynchronous schedule. the operational mode l and valid transitions for this bit are described in section 4 of the ehci specification. 12 hchalted ? ro. 0 = this bit is a 0 when the run/stop bit is a 1. 1 = the host controller sets this bit to 1 afte r it has stopped executin g as a result of the run/stop bit being set to 0, either by soft ware or by the host controller hardware (e.g., internal error). (default) 11:6 reserved 5 interrupt on async advance ? r/wc. system software can forc e the host controller to issue an interrupt the ne xt time the host controller advances the asynchronous schedule by writing a 1 to the interrupt on async advance doorbell bit (d29:f7, d26:f7:caplength + 20h, bit 6) in the usb2.0_cmd register. this bit indicates the assertion of that interrupt source. http://www..net/ datasheet pdf - http://www..net/ ehci controller registers (d29:f7, d26:f7) 640 datasheet 4 host system error ? r/wc. 0 = no serious error occurred during a host sy stem access involving the host controller module 1 = the host controller sets this bit to 1 when a serious error oc curs during a host system access involving the host contro ller module. a hardware interrupt is generated to the system. memory read cycles initiated by the ehc that receive any status other than successful will result in this bit being set. when this error occurs, th e host controller clears the run/stop bit in the usb2.0_cmdregister (d29:f7, d26:f7:caplength + 20h, bit 0) to prevent further execution of the scheduled tds. a hardware interrupt is generate d to the system (if enabled in the interrupt enable register). 3 frame list rollover ? r/wc. 0 = no frame list index rollover from its maximum value to 0. 1 = the host controller sets this bit to a 1 when the frame list index (see section) rolls over from its maximum value to 0. since the ich10 only supports the 1024-entry frame list size, the frame list index rolls over every time frnum13 toggles. 2 port change detect ? r/wc. this bit is allowed to be maintained in the auxiliary power well. alternatively, it is also acceptable that on a d3 to d0 transition of the ehci hc device, this bit is loaded with the or of all of the portsc change bits (including: force port resume, overcurre nt change, enable/disable change and connect status change). regardless of the im plementation, when this bit is readable (i.e., in the d0 state), it must provide a valid vi ew of the port status registers. 0 = no change bit transition from a 0 to 1 or no force port resume bit transition from 0 to 1 as a result of a j-k transiti on detected on a suspended port. 1 = the host controller sets this bi t to 1 when any port for which the port owner bit is set to 0 has a change bit transition fro m a 0 to 1 or a force port resume bit transition from 0 to 1 as a result of a j- k transition detected on a suspended port. 1 usb error interrupt (usberrint) ? r/wc. 0 = no error condition. 1 = the host controller sets this bit to 1 when completion of a usb transaction results in an error condition (e.g., error counter un derflow). if the td on which the error interrupt occurred also had its ioc bit set, both this bit and bit 0 are set. see the ehci specification for a list of the usb errors that will result in this interrupt being asserted. 0 usb interrupt (usbint) ? r/wc. 0 = no completion of a usb transaction whose transfer descriptor had its ioc bit set. no short packet is detected. 1 = the host controller sets this bit to 1 when the cause of an interrupt is a completion of a usb transaction whose transfer descriptor had its ioc bit set. the host controller also sets this bit to 1 when a short packet is detected (actual number of bytes received was less th an the expected number of bytes). bit description http://www..net/ datasheet pdf - http://www..net/ datasheet 641 ehci controller registers (d29:f7, d26:f7) 17.2.2.3 usb2.0_intr?usb 2.0 interrupt enable register offset: mem_base + 28h?2bh attribute: r/w default value: 00000000h size: 32 bits this register enables and disables report ing of the corresponding interrupt to the software. when a bit is set and the corresponding interrupt is active, an interrupt is generated to the host. interrupt sources that ar e disabled in this register still appear in the usb2.0_sts register to allow the software to poll for events. each interrupt enable bit description indicates whether it is depe ndent on the interrupt threshold mechanism (see section 4 of the ehci specification), or not. bit description 31:6 reserved. 5 interrupt on async advance enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1, and th e interrupt on async advance bit (d29:f7, d26:f7:caplength + 24h, bit 5) in the usb2.0_sts register is a 1, the host controller will issue an interrupt at the next interrupt threshol d. the interrupt is acknowledged by software clearing the interrupt on async advance bit. 4 host system error enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1, and th e host system error status bit (d29:f7, d26:f7:caplength + 24h, bit 4) in the usb2.0_sts register is a 1, the host controller will issue an interrupt. the interrupt is acknow ledged by software clearing the host system error bit. 3 frame list rollover enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1, and the frame list rollover bit (d29:f7, d26:f7:caplength + 24h, bit 3) in the usb2.0_sts register is a 1, the host controller will issue an interrupt. the interrupt is acknow ledged by software clearing the frame list rollover bit. 2 port change interrupt enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1, and the port chan ge detect bit (d29:f7, d26:f7:caplength + 24h, bit 2) in the usb2.0_sts register is a 1, the host controller will issue an interrupt. the interrupt is acknow ledged by software clearing the port change detect bit. 1 usb error interrupt enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1, and the usberrint bit (d29:f7, d26:f7:caplength + 24h, bit 1) in the usb2.0_s ts register is a 1, the host controller will issue an interrupt at the next interrupt threshold. the interrupt is acknowledged by software by clearing the usberrint bit in the usb2.0_sts register. 0 usb interrupt enable ? r/w. 0 = disable. 1 = enable. when this bit is a 1, and th e usbint bit (d29:f7, d26:f7:caplength + 24h, bit 0) in the usb2.0_sts register is a 1, the host controller will issue an interrupt at the next interrupt threshold. the interrupt is acknowledged by software by clearing the usbint bit in the usb2.0_sts register. http://www..net/ datasheet pdf - http://www..net/ ehci controller registers (d29:f7, d26:f7) 642 datasheet 17.2.2.4 frindex?frame index register offset: mem_base + 2ch?2fh attribute: r/w default value: 00000000h size: 32 bits the sof frame number value for the bus sof token is derived or alternatively managed from this register. refer to section 4 of the ehci specification for a detailed explanation of the sof value management requirements on the host controller. the value of frindex must be within 125 s (1 micro-fr ame) ahead of the sof token value. the sof value may be implemented as an 11-bit shadow register. for this discussion, this shadow register is 11 bits and is named sofv. sofv updates every 8 micro-frames (1 millisecond). an example implementation to achieve this behavior is to increment sofv each time the frindex[2:0] increments from 0 to 1. software must use the value of frindex to derive the current micro-frame number, both for high-speed isochronous sche duling purposes and to provide the get micro- frame number function required to client dr ivers. therefore, the value of frindex and the value of sofv must be kept consistent if chip is reset or software writes to frindex. writes to frindex must also write-through frindex[13:3] to sofv[10:0]. in order to keep the update as simple as possible, software should never write a frindex value where the three least significant bits are 111b or 000b. note: this register is used by the host controller to index into the periodic frame list. the register updates every 125 microseconds (once each micro-frame). bits [12:3] are used to select a particular entry in the pe riodic frame list during periodic schedule execution. the number of bits used for the index is fixed at 10 for the ich10 since it only supports 1024-entry frame lists. this register must be written as a dword. word and byte writes produce undefined results. this register cannot be written unless the host controller is in the halted state as indicated by the hchalted bit (d29:f7, d26:f7:caplength + 24h, bit 12). a write to this register while the run/stop bit (d29:f7, d26:f7:caplength + 20h, bit 0) is set to a 1 (usb2.0_cmd register) produces undefined results. writes to this register also effect the sof value. see section 4 of the ehci specification for details. bit description 31:14 reserved 13:0 frame list current index/frame number ? r/w. the value in this register increments at the end of each time frame (e.g., micro-frame). bits [12:3] are used for the fr ame list current inde x. this means that each location of the frame list is accessed 8 times (frames or micro-frames) before moving to the next index. http://www..net/ datasheet pdf - http://www..net/ datasheet 643 ehci controller registers (d29:f7, d26:f7) 17.2.2.5 ctrldssegment?contro l data structure segment register offset: mem_base + 30h?33h attribute: r/w, ro default value: 00000000h size: 32 bits this 32-bit register corresponds to the most significant address bits [63:32] for all ehci data structures. since the ich10 hardwi res the 64-bit addressing capability field in hccparams to 1, then this register is used with the link pointers to construct 64-bit addresses to ehci control data structures. this register is concatenated with the link pointer from either the periodiclistb ase, asynclistaddr, or any control data structure link field to construct a 64-bit address. this register allows the host software to locate all control data structures within the same 4 gb memory segment. 17.2.2.6 periodiclistbase?perio dic frame list base address register offset: mem_base + 34h?37h attribute: r/w default value: 00000000h size: 32 bits this 32-bit register contains the beginning address of the periodic frame list in the system memory. since the ich10 host controller operates in 64-bit mode (as indicated by the 1 in the 64-bit addre ssing capability field in the hccsparams register) (offset 08h, bit 0), then the most significant 32 bits of every control data structure address comes from the ctrldssegment register. hcd loads this register prior to starting the schedule execution by the host controller. the memory structure referenced by this physical memory pointer is assumed to be 4-kbyte aligned. the contents of this register are combined with the frame inde x register (frindex) to enable the host controller to step through the periodic frame list in sequence. bit description 31:12 upper address[63:44] ? ro. hardwired to 0s. the ich10 ehc is only capable of generating addresses up to 16 terabytes (44 bits of address). 11:0 upper address[43:32] ? r/w. this 12-bit field corr esponds to address bits 43:32 when forming a control data structure address. bit description 31:12 base address (low) ? r/w. these bits correspon d to memory address signals [31:12], respectively. 11:0 reserved. http://www..net/ datasheet pdf - http://www..net/ ehci controller registers (d29:f7, d26:f7) 644 datasheet 17.2.2.7 asynclistaddr?current asynchronous list address register offset: mem_base + 38h?3bh attribute: r/w default value: 00000000h size: 32 bits this 32-bit register contains the address of the next asynchronous queue head to be executed. since the ich10 host controller oper ates in 64-bit mode (as indicated by a 1 in 64-bit addressing capability field in th e hccparams register) (offset 08h, bit 0), then the most significant 32 bits of every control data structure address comes from the ctrldssegment register (offset 08h). bits [4:0] of this register cannot be modified by system software and will always return 0s when read. the memory structure referenced by this physical memory pointer is assumed to be 32-byte aligned. 17.2.2.8 configflag?configure flag register offset: mem_base + 60h?63h attribute: r/w default value: 00000000h size: 32 bits this register is in the suspend power well. it is only reset by hardware when the suspend power is initially applied or in response to a host controller reset. bit description 31:5 link pointer low (lpl) ? r/w. these bits correspond to memory address signals [31:5], respectively. this field may only reference a queue head (qh). 4:0 reserved. bit description 31:1 reserved. 0 configure flag (cf) ? r/w. host software sets this bit as the last action in its process of configuring the host controller. this bit co ntrols the default port-routing control logic. bit values and side-effects are listed below. see chapter 4 of the ehci specification for operation details. 0 = port routing control logic default-rout es each port to the uhcis (default). 1 = port routing control logic default-rout es all ports to this host controller. http://www..net/ datasheet pdf - http://www..net/ datasheet 645 ehci controller registers (d29:f7, d26:f7) 17.2.2.9 portsc?port n status and control register offset: port 0, port 6: mem_base + 64h ? 67h port 1, port 7: mem_base + 68 ? 6bh port 2, port 8: mem_base + 6c ? 6fh port 3, port 9: mem_base + 70 ? 73h port 4: port 10: mem_base + 74 ? 77h port 5: port 11: mem_base + 78 ? 7bh port 6: mem_base + 7ch-7bh port 7: mem_base + 80h-83h attribute: r/w, r/wc, ro default value: 00003000h size: 32 bits a host controller must implement one or more port registers. software uses the n_port information from the structural parameters register to determine how many ports need to be serviced. all ports have the structure defined below. software must not write to unreported port status and control registers. this register is in the suspend power well. it is only reset by hardware when the suspend power is initially applied or in resp onse to a host controller reset. the initial conditions of a port are: ? no device connected ?port disabled. when a device is attached, the port state transitions to the attached state and system software will process this as with any status change notification. refer to section 4 of the ehci specification for operational requirem ents for how change events interact with port suspend mode. bit description 31:23 reserved. 22 wake on overcurrent enable (wkoc_e) ? r/w. 0 = disable. (default) 1 = enable. writing this bit to a 1 enables th e setting of the pme status bit in the power management control/status register (o ffset 54, bit 15) wh en the overcurrent active bit (bit 4 of this register) is set. 21 wake on disconnect enable (wkdscnnt_e) ? r/w. 0 = disable. (default) 1 = enable. writing this bit to a 1 enables th e setting of the pme status bit in the power management control/status register (offset 54, bit 15) when the current connect status changes from connected to disconnected (i.e., bit 0 of this register changes from 1 to 0). 20 wake on connect enable (wkcnnt_e) ? r/w. 0 = disable. (default) 1 = enable. writing this bit to a 1 enables th e setting of the pme status bit in the power management control/status register (offset 54, bit 15) when the current connect status changes from disconnected to connecte d (i.e., bit 0 of th is register changes from 0 to 1). http://www..net/ datasheet pdf - http://www..net/ ehci controller registers (d29:f7, d26:f7) 646 datasheet 19:16 port test control ? r/w. when this field is 0s, the port is not operating in a test mode. a non-zero value indicates that it is op erating in test mode and the specific test mode is indicated by the specif ic value. the encoding of the test mode bits are (0110b ? 1111b are reserved): refer to usb specification revision 2.0, chapter 7 for details on each test mode. 15:14 reserved. 13 port owner ? r/w. this bit unconditionally goes to a 0 when the configured flag bit in the usb2.0_cmd register makes a 0 to 1 transition. system software uses this fi eld to release ownership of th e port to a selected host controller (in the event that the attached de vice is not a high-spe ed device). software writes a 1 to this bit when the attached device is not a high-speed device. a 1 in this bit means that a companion host controller owns and controls the port. see chapter 4 of the ehci specification for operational details. 12 port power (pp) ? ro. read-only with a value of 1. this indicates that the port does have power. 11:10 line status ? ro.these bits reflect th e current logical levels of the d+ (bit 11) and d? (bit 10) signal lines. these bits are used fo r detection of low-speed usb devices prior to the port reset and enable sequence. this field is valid only when the port enable bit is 0 and the current connect status bit is set to a 1. 00 = se0 10 = j-state 01 = k-state 11 = undefined 9 reserved. bit description value maximum interrupt interval 0000b test mode not enabled (default) 0001b test j_state 0010b test k_state 0011b test se0_nak 0100b test packet 0101b force_enable http://www..net/ datasheet pdf - http://www..net/ datasheet 647 ehci controller registers (d29:f7, d26:f7) 8 port reset ? r/w. when software writes a 1 to this bit (from a 0), the bus reset sequence as defined in the usb specification, revision 2.0 is started. software writes a 0 to this bit to terminate the bus reset sequ ence. software must ke ep this bit at a 1 long enough to ensure the reset sequ ence completes as specified in the usb specification, revision 2.0 . 1 = port is in reset. 0 = port is not in reset. note: when software writes a 0 to this bit, th ere may be a delay before the bit status changes to a 0. the bit st atus will not read as a 0 until after the reset has completed. if the port is in high-speed mode after re set is complete, the host controller will automatically en able this port (e.g., set the port enable bit to a 1). a host controller must terminate the reset and stabilize the state of the port within 2 milliseconds of software transitioning this bit from 0 to 1. for example: if the port de tects that the attached device is high-speed during reset, then the host contro ller must have the port in the enabled state within 2 ms of software writing this bit to a 0. the hchalted bit (d29:f7, d26:f7:caplength + 24h, bit 12) in the usb2.0_sts register should be a 0 before software attempts to use this bit. the host controller may hold port reset asserted to a 1 when the hchalted bit is a 1. this bit is 0 if port power is 0 note: system software should not at tempt to reset a port if the hchalted bit in the usb2.0_sts register is a 1. doing so will result in undefined behavior. 7 suspend ? r/w. 0 = port not in suspend state.(default) 1 = port in suspend state. port enabled bit and suspend bi t of this register define the port states as follows: when in suspend state, downst ream propagation of data is blocked on this port, except for port reset. note that the bit status does not change unt il the port is suspended and that there may be a delay in suspending a po rt depending on the ac tivity on the port. the host controller will unconditionally se t this bit to a 0 when software sets the force port resume bit to a 0 (from a 1). a write of 0 to this bit is ignored by the host controller. if host software sets this bit to a 1 when the port is not enabled (i.e., port enabled bit is a 0) the results are undefined. bit description port enabled suspend port state 0xdisabled 10enabled 11suspend http://www..net/ datasheet pdf - http://www..net/ ehci controller registers (d29:f7, d26:f7) 648 datasheet 6 force port resume ? r/w. 0 = no resume (k-state) detected/driven on port. (default) 1 = resume detected/driven on port. software sets this bit to a 1 to drive resume signaling. the host controller sets this bit to a 1 if a j-to-k transition is detected while the port is in the suspend state. when this bit transitions to a 1 because a j- to-k transition is detected, the port change detect bit (d29:f7, d26:f7:caplength + 24h, bit 2) in the usb2 .0_sts register is also set to a 1. if software sets this bit to a 1, the host controller must not set the port change detect bit. note: when the ehci controller owns the po rt, the resume sequence follows the defined sequence documented in the us b specification, revision 2.0. the resume signaling (full-speed 'k') is driven on the port as long as this bit remains a 1. software must appropriately time the resume and set this bit to a 0 when the appropriate amount of time has elapsed. writing a 0 (from 1) causes the port to return to high-speed mode (forci ng the bus below the port into a high-speed idle). this bit will rema in a 1 until the port has switched to the high-speed idle. 5 overcurrent change ? r/wc. the functionality of this bit is not dependent upon the port owner. software clears th is bit by writing a 1 to it. 0 = no change. (default) 1 = there is a change to overcurrent active. 4 overcurrent active ? ro. 0 = this port does not have an overcurrent condition. (default) 1 = this port currently has an overcurrent condition. this bit will automatically transition from 1 to 0 when the over cu rrent condition is removed. the ich10 automatically disables the port when the overcurrent active bit is 1. 3 port enable/disable change ? r/wc. for the root hub, th is bit gets set to a 1 only when a port is disabled due to the appropri ate conditions existing at the eof2 point (see chapter 11 of the usb specification for th e definition of a port error). this bit is not set due to the disabled-to-enabled transition, nor due to a disconnect. software clears this bit by writing a 1 to it. 0 = no change in status. (default). 1 = port enabled/disabled status has changed. 2 port enabled/disabled ? r/w. ports can only be enabled by the host controller as a part of the reset and enable. so ftware cannot enable a port by writing a 1 to this bit. ports can be disabled by either a fault condition (disconnect event or other fault condition) or by host software . note that the bit status does not change until the port state actually changes. there may be a dela y in disabling or enabling a port due to other host controller and bus events. 0 = disable 1 = enable (default) 1 connect status change ? r/wc. this bit indicates a change has occurred in the port?s current connect status . software sets this bit to 0 by writing a 1 to it. 0 = no change (default). 1 = change in current connect status. the host controller sets this bit for all changes to the port device connect status, even if system software has not cleared an existing connect status change. for example, the insertion status changes twice before system software has cleared the ch anged condition, hub hardware will be ?setting? an already-set bit (i.e ., the bit will remain set). 0 current connect status ? ro. this value reflects the current state of the port, and may not correspond directly to the event th at caused the connec t status change bit (bit 1) to be set. 0 = no device is present. (default) 1 = device is present on port. bit description http://www..net/ datasheet pdf - http://www..net/ datasheet 649 ehci controller registers (d29:f7, d26:f7) 17.2.3 usb 2.0-based debug port register the debug port?s registers are located in th e same memory area, defined by the base address register (mem_base), as the standard ehci registers. the base offset for the debug port registers (a0h) is declared in the debug port base offset capability register at configuration offset 5ah (d29:f7, d26:f7:offset 5ah). the specific ehci port that supports this debug capability (port 0 for d29: f7 and port 6 for d26:f7) is indicated by a 4-bit field (bits 20?23) in the hcsparams re gister of the ehci controller. the address map of the debug port registers is shown in ta b l e 1 7 - 4 . notes: 1. all of these registers are implemented in the core well and re set by pltrst#, ehc hcreset, and a ehc d3-to-d0 transition. 2. the hardware associated with this register provides no chec ks to ensure that software programs the interface correctly. how th e hardware behaves when programmed improperly is undefined. table 17-4. debug port register address map mem_base + offset mnemonic register name default type a0?a3h cntl_sts control/status 00000000h r/w, r/wc, ro a4?a7h usbpid usb pids 00000000h r/w, ro a8?afh databuf[7:0] data buffer (bytes 7:0) 00000000 00000000h r/w b0?b3h config configuration 00007f01h r/w http://www..net/ datasheet pdf - http://www..net/ ehci controller registers (d29:f7, d26:f7) 650 datasheet 17.2.3.1 cntl_sts?control/status register offset: mem_base + a0h attribute: r/w, r/wc, ro default value: 00000000h size: 32 bits bit description 31 reserved 30 owner_cnt ? r/w. 0 = ownership of the debug port is not fo rced to the ehci controller (default) 1 = ownership of the debug port is forced to the ehci controller (i.e. immediately taken away from the companion classic usb host controller) if the port was already owned by the ehci controller, then setting this bit has no effect. this bit overrides all of the owners hip-related bits in the standard ehci registers. 29 reserved 28 enabled_cnt ? r/w. 0 = software can clear this by writing a 0 to it. the hardware clears this bit for the same conditions where the port enable/disable change bit (in the portsc register) is set. (default) 1 = debug port is enabled for operation. soft ware can directly set this bit if the port is already enabled in the as sociated portsc register (this is enforced by the hardware). 27:17 reserved 16 done_sts ? r/wc. software can clear this by writing a 1 to it. 0 = request not complete 1 = set by hardware to indicate that the request is complete. 15:12 link_id_sts ? ro. this field identifi es the link interface. 0h = hardwired. indicates th at it is a usb debug port. 11 reserved. 10 in_use_cnt ? r/w. set by software to indicate th at the port is in use. cleared by software to indicate that th e port is free and may be used by other software. this bit is cleared after reset. (this bi t has no affect on hardware.) 9:7 exception_sts ? ro. this field indicates the exception when the error_good#_sts bit is set. this field should be ignored if the error_good#_sts bit is 0. 000 = no error. (default) note: this should not be seen since this field should only be checked if there is an error. 001 = transaction error: indicates the usb 2.0 transaction had an error (crc, bad pid, timeout, etc.) 010 = hardware error. requ est was attempted (or in progress) when port was suspended or reset. all other combinations are reserved 6 error_good#_sts ? ro. 0 = hardware clears this bit to 0 after the proper comp letion of a read or write. (default) 1 = error has occurred. details on the natu re of the error are provided in the exception field. http://www..net/ datasheet pdf - http://www..net/ datasheet 651 ehci controller registers (d29:f7, d26:f7) notes: 1. software should do read-modify-write operations to this register to preserve the contents of bits not being modified. this include reserved bits. 2. to preserve the usage of reserved bits in the future, software sh ould always write the same value read from the bit unti l it is defined. reserved bits will always return 0 when read. 5 go_cnt ? r/w. 0 = hardware clears this bit when hardwa re sets the done_sts bit. (default) 1 = causes hardware to perform a read or write request. note: writing a 1 to this bit when it is alre ady set may result in undefined behavior. 4 write_read#_cnt ? r/w. software clears this bit to indicate that the current request is a read. softwa re sets this bit to indicate that the current request is a write. 0 = read (default) 1 = write 3:0 data_len_cnt ? r/w. this field is used to indicate the size of the data to be transferred. default = 0h. for write operations, this field is set by software to indicate to the hardware how many bytes of data in data buffer are to be transferred to the console. a value of 0h indicates that a zero-length packet should be sent. a value of 1?8 indicates 1?8 bytes are to be transferred. values 9?fh are invalid and how hardware behaves if used is undefined. for read operations, this fiel d is set by hardware to indicate to software how many bytes in data buffer are valid in response to a read operation. a value of 0h indicates that a zero length packet was returned and the state of data buffe r is not defined. a value of 1?8 indicates 1?8 by tes were received. hardware is not allowed to return values 9?fh. the transferring of data always starts with byte 0 in the data area and moves toward byte 7 until the transfer size is reached. bit description http://www..net/ datasheet pdf - http://www..net/ ehci controller registers (d29:f7, d26:f7) 652 datasheet 17.2.3.2 usbpid?usb pids register offset: mem_base + a4h?a7h attribute: r/w, ro default value: 00000000h size: 32 bits this dword register is used to communicate pid information between the usb debug driver and the usb debug port. the debug port uses some of these fields to generate usb packets, and uses other fields to retu rn pid information to the usb debug driver. 17.2.3.3 databuf[7:0]?data buffer bytes[7:0] register offset: mem_base + a8h?afh attribute: r/w default value: 0000000000000000h size: 64 bits this register can be accessed as 8 separate 8-bit registers or 2 separate 32-bit register. 17.2.3.4 config?configuration register offset: mem_base + b0?b3h attribute: r/w default value: 00007f01h size: 32 bits bit description 31:24 reserved. 23:16 received_pid_sts[23:16] ? ro. hardware updates this field with the received pid for transactions in either direction. when the controller is writing data, this field is updated with the handshake pid that is received from the devi ce. when the host controller is reading data, this field is updated with the da ta packet pid (if the device sent data), or the handshake pid (if the devi ce naks the request). this field is valid when the hardware clears the go_done#_cnt bit. 15:8 send_pid_cnt[15:8] ? r/w. hardware sends this pid to begin the data packet when sending data to usb (i.e., write_re ad#_cnt is asserted). software typically sets this field to either data0 or data1 pid values. 7:0 token_pid_cnt[7:0] ? r/w. hardware sends this pid as the token pid for each usb transaction. software typically sets this field to either in, out, or setup pid values. bit description 63:0 databuffer[63:0] ? r/w. this field is the 8 byte s of the data buffer. bits 7:0 correspond to least significant byte (byt e 0). bits 63:56 correspond to the most significant byte (byte 7). the bytes in the data buffer must be written with data before soft ware initiates a write request. for a read re quest, the data buffer contains valid data when done_sts bit (offset a0, bit 16) is cleared by the hardwa re, error_good#_sts (offset a0, bit 6) is cleared by the hardware, and the data_l ength_cnt field (offs et a0, bits 3:0) indicates the number of bytes that are valid. bit description 31:15 reserved 14:8 usb_address_cnf ? r/w. this 7-bit field identifies the usb device address used by the controller for all token pid generation. (default = 7fh) 7:4 reserved 3:0 usb_endpoint_cnf ? r/w. this 4-bit field identifies the endpoint used by the controller for all token pid generation. (default = 1h) http://www..net/ datasheet pdf - http://www..net/ datasheet 653 intel ? high definition audio controller registers (d27:f0) 18 intel ? high definition audio controller registers (d27:f0) the intel high definition audio controller resi des in pci device 27, function 0 on bus 0. this function contains a set of dma engines that are used to move samples of digitally encoded data between system memory and external codecs. note: all registers in this function (including me mory-mapped registers) must be addressable in byte, word, and d-word quantities. th e software must always make register accesses on natural boundaries (i.e. d-word accesses must be on d-word boundaries; word accesses on word boundaries, etc.) in addition, the memory-mapped register space must not be accessed with the lock semantic exclusive-access mechanism. if software attempts exclusive-access mechanisms to the intel high definition audio memory-mapped space, the results are undefined. note: users interested in providing feedback on th e intel high definition audio specification or planning to implement the intel high definition audio specification into a future product will need to execute the intel ? high definition audio specification developer?s agreement . for more information, contact nextgenaudio@intel.com. 18.1 intel ? high definition audio pci configuration space (intel ? high definition audio? d27:f0) note: address locations that are not shown should be treated as reserved. table 18-1. intel ? high definition audio pci register address map (intel ? high definition audio d27:f0) (sheet 1 of 2) offset mnemonic register name default access 00h?01h vid vendor identification 8086h ro 02h?03h did device identification see register description ro 04h?05h pcicmd pci command 0000h r/w, ro 06h?07h pcists pci status 0010h r/wc, ro 08h rid revision identification see register description ro 09h pi programming interface 00h ro 0ah scc sub class code 03h ro 0bh bcc base class code 04h ro 0ch cls cache line size 00h r/w 0dh lt latency timer 00h ro 0eh headtyp header type 00h ro 10h?13h hdbarl intel ? high definition audio lower base address (memory) 00000004h r/w, ro 14h?17h hdbaru intel high definition audio upper base address (memory) 00000000h r/w 2ch?2dh svid subsystem vendor identification 0000h r/wo http://www..net/ datasheet pdf - http://www..net/ intel ? high definition audio controller registers (d27:f0) 654 datasheet 2eh?2fh sid subsystem identification 0000h r/wo 34h capptr capability list pointer 50h ro 3ch intln interrupt line 00h r/w 3dh intpn interrupt pin see register description ro 40h hdctl intel high definiti on audio control 01h r/w, ro 44h tcsel traffic class select 00h r/w 50h?51h pid pci power management capability id 6001h r/wo, ro 52h?53h pc power management capabilities c842h ro 54h?57h pcs power management control and status 00000000h r/w, ro, r/wc 60h?61h mid msi capability id 7005h ro 62h?63h mmc msi message control 0080h r/w, ro 64h?67h mmla msi message lower address 00000000h r/w, ro 68h?6bh mmua smi message upper address 00000000h r/w 6ch?6dh mmd msi message data 0000h r/w 70h?71h pxid pci express* capability identifiers 0010h ro 72h?73h pxc pci express capabilities 0091h ro 74h?77h devcap device capabilities 10000000h ro, r/wo 78h?79h devc device control 0800h r/w, ro 7ah?7bh devs device status 0010h ro 100h?103h vccap virtual channel enhanced capability header 13010002h r/wo 104h?107h pvccap1 port vc capability register 1 00000001h ro 108h?10bh pvccap2 port vc capability register 2 00000000h ro 10ch?10d pvcctl port vc control 0000h ro 10eh?10fh pvcsts port vc status 0000h ro 110h?113h vc0cap vc0 resource capability 00000000h ro 114h?117h vc0ctl vc0 resource control 800000ffh r/w, ro 11ah?11bh vc0sts vc0 resource status 0000h ro 11ch?11fh vcicap vci resource capability 00000000h ro 120h?123h vcictl vci resource control 00000000h r/w, ro 126h?127h vcists vci resource status 0000h ro 130h?133h rccap root complex link declaration enhanced capability header 00010005h ro 134h?137h esd element self description 0f000100h ro 140h?143h l1desc link 1 description 00000001h ro 148h?14bh l1addl link 1 lower address see register description ro 14ch?14fh l1addu link 1 upper address 00000000h ro table 18-1. intel ? high definition audio pci register address map (intel ? high definition audio d27:f0) (sheet 2 of 2) http://www..net/ datasheet pdf - http://www..net/ datasheet 655 intel ? high definition audio controller registers (d27:f0) 18.1.1 vid?vendor identi fication register (intel ? high definition au dio controller?d27:f0) offset: 00h-01h attribute: ro default value: 8086h size: 16 bits 18.1.2 did?device identification register (intel ? high definition au dio controller?d27:f0) offset address: 02h ? 03h attribute: ro default value: see bit description size: 16 bits 18.1.3 pcicmd?pci command register (intel ? high definition au dio controller?d27:f0) offset address: 04h ? 05h attribute: r/w, ro default value: 0000h size: 16 bits bit description 15:0 vendor id ? ro. this is a 16-bit value assigned to intel. intel vid = 8086h bit description 15:0 device id ? ro. this is a 16-bit value assigned to the intel ? ich10 intel high definition audio controller. refer to the intel ? i/o controller hub (ich10) family specification update for the value of the device id register. bit description 15:11 reserved 10 interrupt disable (id) ? r/w. 0= the intx# signals may be asserted. 1= the intel ? high definition audio controller?s intx# signal will be de-asserted. note: that this bit does not affect the generation of msi?s. 9 fast back to back enable (fbe) ? ro. not implemented. hardwired to 0. 8 serr# enable (serr_en) ? r/w. serr# is not generated by the ich10 intel high definition audio controller. 7 wait cycle control (wcc) ? ro. no t implemented. hardwired to 0. 6 parity error response (per ) ? r/w. not implemented. 5 vga palette snoop (vps). not implemented. hardwired to 0. 4 memory write and invalidate enable (mwie) ? ro. not implemented. hardwired to 0. 3 special cycle enable (sce). no t implemented. hardwired to 0. http://www..net/ datasheet pdf - http://www..net/ intel ? high definition audio controller registers (d27:f0) 656 datasheet 18.1.4 pcists?pci status register (intel ? high definition audio controller?d27:f0) offset address: 06h ? 07h attribute: ro, r/wc default value: 0010h size: 16 bits 2 bus master enable (bme) ? r/w. controls standard pci express* bus mastering capabilities for memory and i/o, reads and wr ites. note that this bit also controls msi generation since msi?s are essentially memory writes. 0 = disable 1 = enable 1 memory space enable (mse) ? r/w. enables memory space addresses to the intel high definition audio controller. 0 = disable 1 = enable 0 i/o space enable (iose)?ro. hardwired to 0 since the intel high definition audio controller does not implement i/o space. bit description bit description 15 detected parity error (dpe) ? ro . not implemented. hardwired to 0. 14 serr# status (serrs) ? ro. not implemented. hardwired to 0. 13 received master abort (rma) ? r/wc. software clears this bit by writing a 1 to it. 0 = no master abort received. 1 = the intel ? high definition audio co ntroller sets this bit when, as a bus master, it receives a master abort. when set, the intel high definition audio controller clears the run bit for the chan nel that received the abort. 12 received target abort (rta) ? ro. not implemented. hardwired to 0. 11 signaled target abort (sta) ? ro. not implemented. hardwired to 0. 10:9 devsel# timing status (dev_sts) ? ro. does not apply. hardwired to 0. 8 data parity error detected (dped) ? ro. not implemented. hardwired to 0. 7 fast back to back capable (fb2bc) ? ro. does not apply. hardwired to 0. 6 reserved. 5 66 mhz capable (66mhz_cap) ? ro. does not apply. hardwired to 0. 4 capabilities list (cap_list) ? ro. hardwired to 1. indicate s that the controller contains a capabilities poin ter list. the first item is pointed to by looking at configuration offset 34h. 3 interrupt status (is) ? ro. 0 = this bit is 0 after th e interrupt is cleared. 1 = this bit is 1 when the intx# is asserted. note that this bit is not set by an msi. 2:0 reserved. http://www..net/ datasheet pdf - http://www..net/ datasheet 657 intel ? high definition audio controller registers (d27:f0) 18.1.5 rid?revision identification register (intel ? high definition au dio controller?d27:f0) offset: 08h attribute: ro default value: see bit description size: 8 bits 18.1.6 pi?programming interface register (intel ? high definition au dio controller?d27:f0) offset: 09h attribute: ro default value: 00h size: 8 bits 18.1.7 scc?sub class code register (intel ? high definition au dio controller?d27:f0) address offset: 0ah attribute: ro default value: 03h size: 8 bits 18.1.8 bcc?base clas s code register (intel ? high definition au dio controller?d27:f0) address offset: 0bh attribute: ro default value: 04h size: 8 bits 18.1.9 cls?cache line size register (intel ? high definition au dio controller?d27:f0) address offset: 0ch attribute: r/w default value: 00h size: 8 bits bit description 7:0 revision id ? ro. refer to the intel ? i/o controller hub (ich10) family specification update for the value of the revision id register bit description 7:0 programming interface ? ro. bit description 7:0 sub class code (scc) ? ro. 03h = audio device bit description 7:0 base class code (bcc) ? ro. 04h = multimedia device bit description 7:0 cache line size ? r/w. implemented as r/w register, but has no functional impact to the ich10 http://www..net/ datasheet pdf - http://www..net/ intel ? high definition audio controller registers (d27:f0) 658 datasheet 18.1.10 lt?latency timer register (intel ? high definition audio controller?d27:f0) address offset: 0dh attribute: ro default value: 00h size: 8 bits 18.1.11 headtyp?header type register (intel ? high definition audio controller?d27:f0) address offset: 0eh attribute: ro default value: 00h size: 8 bits 18.1.12 hdbarl?intel ? high definition audio lower base address register (intel ? high definition audio?d27:f0) address offset: 10h-13h attribute: r/w, ro default value: 00000004h size: 32 bits 18.1.13 hdbaru?intel ? high definition audio upper base address register (intel ? high definition audio controller?d27:f0) address offset: 14h-17h attribute: r/w default value: 00000000h size: 32 bits bit description 7:0 latency timer ? ro. hardwired to 00 bit description 7:0 header type ? ro. hardwired to 00. bit description 31:14 lower base a ddress (lba) ? r/w. base address for the intel ? high definition audio controller?s memory mapped configuration registers. 16 kbytes are requested by hardwiring bits 13:4 to 0s. 13:4 reserved. 3 prefetchable (pref) ? ro. hardwired to 0 to indicate that this bar is not prefetchable 2:1 address range (addrng) ? ro. hardwired to 10b, indicating that this bar can be located anywhere in 64-bit address space. 0 space type (sptyp) ? ro. hardwired to 0. indicates this bar is located in memory space. bit description 31:0 upper base address (uba) ? r/w. upper 32 bits of th e base address for the intel ? high definition audio controller?s memory mapped configuration registers. http://www..net/ datasheet pdf - http://www..net/ datasheet 659 intel ? high definition audio controller registers (d27:f0) 18.1.14 svid?subsystem vendor identification register (intel ? high definition au dio controller?d27:f0) address offset: 2ch?2dh attribute: r/wo default value: 0000h size: 16 bits function level reset: no the svid register, in combination with the subsystem id register (d27:f0:2eh), enable the operating environment to distinguish one audio subsystem from the other(s). this register is implemented as write-once register. once a value is written to it, the value can be read back. any subsequent writes will have no effect. this register is not affected by the d3 hot to d0 transition. 18.1.15 sid?subsystem iden tification register (intel ? high definition au dio controller?d27:f0) address offset: 2eh ? 2fh attribute: r/wo default value: 0000h size: 16 bits function level reset: no the sid register, in combination with the subsystem vendor id register (d27:f0:2ch) make it possible for the operating enviro nment to distinguish one audio subsystem from the other(s). this register is implemented as write-once register. once a value is written to it, the value can be read back. any subsequent writes will have no effect. this register is not affected by the d3 hot to d0 transition. t 18.1.16 capptr?capabilit ies pointer register (intel ? high definition au dio controller?d27:f0) address offset: 34h attribute: ro default value: 50h size: 8 bits this register indicates the offset for the capability pointer. bit description 15:0 subsystem vendor id ? r/wo. bit description 15:0 subsystem id ? r/wo. bit description 7:0 capabilities pointer (cap_ptr) ? ro. this field indicates that the first capability pointer offset is o ffset 50h (power management capability) http://www..net/ datasheet pdf - http://www..net/ intel ? high definition audio controller registers (d27:f0) 660 datasheet 18.1.17 intln?interrupt line register (intel ? high definition audio controller?d27:f0) address offset: 3ch attribute: r/w default value: 00h size: 8 bits 18.1.18 intpn?interrupt pin register (intel ? high definition audio controller?d27:f0) address offset: 3dh attribute: ro default value: see description size: 8 bits 18.1.19 hdctl?intel ? high definition audio control register (intel ? high definition audio controller?d27:f0) address offset: 40h attribute: ro default value: 01h size: 8 bits bit description 7:0 interrupt line (int_ln) ? r/w. this data is not used by the intel ? ich10. it is used to communicate to software the interrupt line that the interrupt pin is connected to. bit description 7:4 reserved. 3:0 interrupt pin ? ro. this reflects the value of d27ip.zip (chipset config registers:offset 3110h:bits 3:0). bit description 7:1 reserved. 0 intel ? high definition signal mode ? ro. this bit is hardwired to 1 (high definition audio mode) http://www..net/ datasheet pdf - http://www..net/ datasheet 661 intel ? high definition audio controller registers (d27:f0) 18.1.20 tcsel?traffic cl ass select register (intel ? high definition au dio controller?d27:f0) address offset: 44h attribute: r/w default value: 00h size: 8 bits function level reset: no this register assigned the value to be placed in the tc field. corb and rirb data will always be assigned tc0. 18.1.21 pid?pci power management capability id register (intel ? high definition au dio controller?d27:f0) address offset: 50h-51h attribute: r/wo, ro default value: 6001h size: 16 bits function level reset: no (bits 7:0 only) bit description 7:3 reserved. 2:0 intel ? high definition audio traffi c class assignment (tcsel) ? r/w. this register assigns the valu e to be placed in the traffic class field for input data, output data, and buffer de scriptor transactions. 000 = tc0 001 = tc1 010 = tc2 011 = tc3 100 = tc4 101 = tc5 110 = tc6 111 = tc7 note: these bits are not reset on d3 hot to d0 transition; however, they are reset by pltrst#. bit description 15:8 next capability (next) ? r/wo. points to the next capability structure (msi). 7:0 cap id (cap) ? ro. hardwired to 01h. indicates that this pointer is a pci power management capability. th ese bits are not reset by function level reset. http://www..net/ datasheet pdf - http://www..net/ intel ? high definition audio controller registers (d27:f0) 662 datasheet 18.1.22 pc?power management capabilities register (intel ? high definition audio controller?d27:f0) address offset: 52h-53h attribute: ro default value: c842h size: 16 bits bit description 15:11 pme support ? ro. hardwired to 11001b. indicates pme# can be generated from d3 and d0 states. 10 d2 support ? ro. hardwired to 0. indi cates that d2 state is not supported. 9 d1 support ?ro. hardwired to 0. indi cates that d1 state is not supported. 8:6 aux current ? ro. hardwired to 001b. reports 55 ma maximum suspend well current required when in the d3 cold state. 5 device specific initialization (dsi) ? ro. ha rdwired to 0. indicates that no device specific initialization is required. 4 reserved 3 pme clock (pmec) ? ro. does not apply. hardwired to 0. 2:0 version ? ro. hardwired to 010b. indicates support for version 1.1 of the pci power management specification. http://www..net/ datasheet pdf - http://www..net/ datasheet 663 intel ? high definition audio controller registers (d27:f0) 18.1.23 pcs?power management co ntrol and status register (intel ? high definition au dio controller?d27:f0) address offset: 54h-57h attribute: ro, r/w, r/wc default value: 00000000h size: 32 bits function level reset: no bit description 31:24 data ? ro. does not apply. hardwired to 0. 23 bus power/clock control enable ? ro . does not apply. hardwired to 0. 22 b2/b3 support ? ro. does not apply. hardwired to 0. 21:16 reserved. 15 pme status (pmes) ? r/wc. 0 = software clears the bit by writing a 1 to it. 1 = this bit is set when the intel ? high definition audio controller would normally assert the pme# signal independent of the state of the pme_en bit (bit 8 in this register). this bit is in the resume well and is clea red by a power-on reset. software must not make assumptions about the reset state of this bit and must se t it appropriately. 14:9 reserved 8 pme enable (pmee) ? r/w. 0 = disable 1 = when set and if corresponding pmes also set, the intel high definition audio controller sets the pme_b0_sts bit in the gpe0_sts register (pmbase +28h). this bit in the resume well an d is cleared on a power-on re set. software must not make assumptions about the reset state of this bit and must set it appropriately. 7:2 reserved 1:0 power state (ps) ? r/w. this field is used both to determine the current power state of the intel high definition audio co ntroller and to set a new power state. 00 = d0 state 11 = d3 hot state others = reserved notes: 1. if software attempts to wr ite a value of 01b or 10b in to this field, the write operation must complete normally; howeve r, the data is discarded and no state change occurs. 2. when in the d3 hot states, the intel high definition audio controller?s configuration space is available, but the io and memory space are not. additionally, interrupts are blocked. 3. when software changes this value from d3 hot state to the d0 st ate, an internal warm (soft) reset is generated, and so ftware must re-initialize the function. http://www..net/ datasheet pdf - http://www..net/ intel ? high definition audio controller registers (d27:f0) 664 datasheet 18.1.24 mid?msi capability id register (intel ? high definition audio controller?d27:f0) address offset: 60h-61h attribute: ro default value: 7005h size: 16 bits 18.1.25 mmc?msi messag e control register (intel ? high definition audio controller?d27:f0) address offset: 62h-63h attribute: ro, r/w default value: 0080h size: 16 bits 18.1.26 mmla?msi message lower address register (intel ? high definition audio controller?d27:f0) address offset: 64h-67h attribute: ro, r/w default value: 00000000h size: 32 bits 18.1.27 mmua?msi message upper address register (intel ? high definition audio controller?d27:f0) address offset: 68h-6bh attribute: r/w default value: 00000000h size: 32 bits bit description 15:8 next capability (next) ? ro. hardwired to 70h. points to the pci express* capability structure. 7:0 cap id (cap) ? ro. hardwired to 05h. indicates th at this pointer is a msi capability bit description 15:8 reserved 7 64b address capability (64add) ? ro. hardwired to 1. indicates the ability to generate a 64-bit message address 6:4 multiple message enable (mme) ? ro. normally this is a r/w register. however since only 1 message is supported, these bits are hardwired to 000 = 1 message. 3:1 multiple message capable (mmc) ? ro. ha rdwired to 0 indicating request for 1 message. 0 msi enable (me) ? r/w. 0 = an msi may not be generated 1 = an msi will be generated instead of an intx signal. bit description 31:2 message lower address (mla) ? r/w. lower address used for msi message. 1:0 reserved. bit description 31:0 message upper address (mua) ? r/w. upper 32-bits of address used for msi message. http://www..net/ datasheet pdf - http://www..net/ datasheet 665 intel ? high definition audio controller registers (d27:f0) 18.1.28 mmd?msi message data register (intel ? high definition au dio controller?d27:f0) address offset: 6ch-6dh attribute: r/w default value: 0000h size: 16 bits 18.1.29 pxid?pci express* capability id register (intel ? high definition au dio controller?d27:f0) address offset: 70h-71h attribute: ro default value: 0010h size: 16 bits 18.1.30 pxc?pci express* capabilities register (intel ? high definition au dio controller?d27:f0) address offset: 72h-73h attribute: ro default value: 0091h size: 16 bits bit description 15:0 message data (md) ? r/w. data used for msi message. bit description 15:8 next capability (next) ? ro. hardwired to 0. indicates that this is the last capability structure in the list. 7:0 cap id (cap) ? ro. hardwired to 10h. indicates th at this pointer is a pci express* capability structure bit description 15:14 reserved 13:9 interrupt message number (imn) ? ro. hardwired to 0. 8 slot implemented (si) ? ro. hardwired to 0. 7:4 device/port type (dpt) ? ro. hardwired to 1001b. indicates that this is a root complex integrated endpoint device. 3:0 capability version (cv) ? ro. hardwired to 0001b. indicates version #1 pci express capability http://www..net/ datasheet pdf - http://www..net/ intel ? high definition audio controller registers (d27:f0) 666 datasheet 18.1.31 devcap?device ca pabilities register (intel ? high definition audio controller?d27:f0) address offset: 74h-77h attribute: r/wo, ro default value: 10000000h size: 32 bits function level reset: no bit description 31:29 reserved 28 function level reset (flr) ? r/wo. a 1 indicates that the ich10 hd audio controller supports the functi on level reset capability. 27:26 captured slot power limit sc ale (spls) ? ro. hardwired to 0. 25:18 captured slot power limit value (splv) ? ro. hardwired to 0. 17:15 reserved 14 power indicator present ? ro. hardwired to 0. 13 attention indicator present ? ro. hardwired to 0. 12 attention button present ? ro. hardwired to 0. 11:9 endpoint l1 acceptable latency ? r/wo. 8:6 endpoint l0s acceptable latency ? r/wo. 5 extended tag field support ? ro. hardwired to 0. indicates 5-bit tag field support 4:3 phantom functions supported ? ro. hardwired to 0. indicates that phantom functions not supported 2:0 max payload size supported ? ro. hardwired to 0. indicates 128-b maximum payload size capability http://www..net/ datasheet pdf - http://www..net/ datasheet 667 intel ? high definition audio controller registers (d27:f0) 18.1.32 devc?device control register (intel ? high definition au dio controller?d27:f0) address offset: 78h-79h attribute: r/w, ro default value: 0800h size: 16 bits function level reset: no (bit 11 only) bit description 15 initiate flr (if) ? r/w. this bit is used to initiate flr transition. 1 = a write of 1 initiates flr transition. since hardware does not respond to any cycles until flr completion, the read valu e by software from this bit is 0. 14:12 max read request size ? ro. hardwired to 0 enabling 128b maximum read request size. 11 no snoop enable (nsnpen) ? r/w. 0 = the intel ? high definition audio controller will not set the no snoop bit. in this case, isochronous transfers will not use vc1 (vci) even if it is enabled since vc1 is never snooped. isochronous transfers will use vc0. 1 = the intel high definition audio controller is permitted to set th e no snoop bit in the requester attributes of a bus master transa ction. in this case, vc0 or vc1 may be used for isochronous transfers. note: this bit is not reset on d3 hot to d0 transition; however, it is reset by pltrst#. this bit is not reset by function level reset. 10 auxiliary power enable ? ro. hardwired to 0, indicating that intel high definition audio device does not draw aux power 9 phantom function enable ? ro. hardwi red to 0 disabling phantom functions. 8 extended tag field enable ? ro. hardwired to 0 enabling 5-bit tag. 7:5 max payload size ? ro. hardwired to 0 indicating 128b. 4 enable relaxed ordering ? ro. hardwi red to 0 disabling relaxed ordering. 3 unsupported request reporting enable ? r/w. not implemented. 2 fatal error reporting enable ? r/w. not implemented. 1 non-fatal error reporting en able ? r/w. not implemented. 0 correctable error reporting en able ? r/w. not implemented. http://www..net/ datasheet pdf - http://www..net/ intel ? high definition audio controller registers (d27:f0) 668 datasheet 18.1.33 devs?device status register (intel ? high definition audio controller?d27:f0) address offset: 7ah-7bh attribute: ro default value: 0010h size: 16 bits 18.1.34 vccap?virtual channel enhanced capability header (intel ? high definition audio controller?d27:f0) address offset: 100h-103h attribute: r/wo default value: 13010002h size: 32 bits bit description 15:6 reserved 5 transactions pending ? ro. 0 = indicates that completions for all no n-posted requests have been received 1 = indicates that intel ? high definition audio contro ller has issued non-posted requests which have not been completed. 4 aux power detected ? ro. hardwired to 1 indicating the device is connected to resume power 3 unsupported request detected ? ro . not implemented. hardwired to 0. 2 fatal error detected ? ro. no t implemented. hardwired to 0. 1 non-fatal error detected ? ro. not implemented. hardwired to 0. 0 correctable error detected ? ro. not implemented. hardwired to 0. bit description 31:20 next capability offset ? r/wo. points to the next capability header. 130h = root complex link declar ation enhanced capability header 000h = root complex link declaration enha nced capability header is not supported. 19:16 capability version ? r/wo. 0h = pci express virtual channel capability and the root complex topology capability structure are not supported. 1h = pci express virtual channel capability and the root complex topology capability structure are supported. 15:0 pci express* extended capability ? r/wo. 0000h =pci express virtual channel capa bility and the root complex topology capability structure are not supported. 0002h =pci express virtual channel capa bility and the root complex topology capability structure are supported. http://www..net/ datasheet pdf - http://www..net/ datasheet 669 intel ? high definition audio controller registers (d27:f0) 18.1.35 pvccap1?port vc capability register 1 (intel ? high definition au dio controller?d27:f0) address offset: 104h-107h attribute: ro default value: 00000001h size: 32 bits 18.1.36 pvccap2 ? port vc capability register 2 (intel ? high definition au dio controller?d27:f0) address offset: 108h-10bh attribute: ro default value: 00000000h size: 32 bits 18.1.37 pvcctl ? port vc control register (intel ? high definition au dio controller?d27:f0) address offset: 10ch-10dh attribute: ro default value: 0000h size: 16 bits bit description 31:12 reserved. 11:10 port arbitration table entry size ? ro. hard wired to 0 since this is an endpoint device. 9:8 reference clock ? ro. hardwired to 0 since this is an endpoint device. 7 reserved. 6:4 low priority extended vc count ? ro. hardwired to 0. indicates that only vc0 belongs to the low priority vc group 3 reserved. 2:0 extended vc count ? ro. hardwired to 001b. indicates that 1 extended vc (in addition to vc0) is supported by the intel ? high definition audio controller. bit description 31:24 vc arbitration table offset ? ro. hardwired to 0 indicating that a vc arbitration table is not present. 23:8 reserved. 7:0 vc arbitration capability ? ro. hardwired to 0. these bits are not applicable since the intel ? high definition audio controller report s a 0 in the low priority extended vc count bits in the pvccap1 register. bit description 15:4 reserved. 3:1 vc arbitration select ? ro. hardwired to 0. normally these bits are r/w. however, these bits are not applicable since the intel ? high definition audio controller reports a 0 in the low priority extended vc count bits in the pvccap1 register 0 load vc arbitration table ? ro. hardwired to 0 since an arbitration table is not present. http://www..net/ datasheet pdf - http://www..net/ intel ? high definition audio controller registers (d27:f0) 670 datasheet 18.1.38 pvcsts?port vc status register (intel ? high definition audio controller?d27:f0) address offset: 10eh-10fh attribute: ro default value: 0000h size: 16 bits 18.1.39 vc0cap?vc0 resour ce capability register (intel ? high definition audio controller?d27:f0) address offset: 110h-113h attribute: ro default value: 00000000h size: 32 bits bit description 15:1 reserved. 0 vc arbitration table status ? ro. hardwire d to 0 since an arbitration table is not present. bit description 31:24 port arbitration table offset ? ro. hardwire d to 0 since this field is not valid for endpoint devices 23 reserved. 22:16 maximum time slots ? ro. hardwired to 0 si nce this field is not valid for endpoint devices 15 reject snoop transactions ? ro. hardwired to 0 since this field is not valid for endpoint devices. 14 advanced packet switching ? ro. hardwired to 0 since this field is not valid for endpoint devices 13:8 reserved. 7:0 port arbitration capability ? ro. hardwired to 0 since this field is not valid for endpoint devices http://www..net/ datasheet pdf - http://www..net/ datasheet 671 intel ? high definition audio controller registers (d27:f0) 18.1.40 vc0ctl?vc0 reso urce control register (intel ? high definition au dio controller?d27:f0) address offset: 114h-117h attribute: r/w, ro default value: 800000ffh size: 32 bits function level reset: no 18.1.41 vc0sts?vc0 resource status register (intel ? high definition au dio controller?d27:f0) address offset: 11ah-11bh attribute: ro default value: 0000h size: 16 bits bit description 31 vc0 enable ? ro. hardwired to 1 for vc0. 30:27 reserved. 26:24 vc0 id ? ro. hardwired to 0 since th e first vc is always assigned as vc0. 23:20 reserved. 19:17 port arbitration select ? ro. hardwired to 0 since this field is not valid for endpoint devices. 16 load port arbitration table ? ro. hardwired to 0 since this field is not valid for endpoint devices. 15:8 reserved. 7:0 tc/vc0 map ? r/w, ro. bit 0 is hardwired to 1 si nce tc0 is always mapped vc0. bits [7:1] are implemented as r/w bits. bit description 15:2 reserved. 1 vc0 negotiation pending ? ro. hardwired to 0 since this bit does not apply to the integrated intel ? high definition audio device. 0 port arbitration table status ? ro. hardwire d to 0 since this field is not valid for endpoint devices. http://www..net/ datasheet pdf - http://www..net/ intel ? high definition audio controller registers (d27:f0) 672 datasheet 18.1.42 vcicap?vci resour ce capability register (intel ? high definition audio controller?d27:f0) address offset: 11ch-11fh attribute: ro default value: 00000000h size: 32 bits 18.1.43 vcictl?vci reso urce control register (intel ? high definition audio controller?d27:f0) address offset: 120h-123h attribute: r/w, ro default value: 00000000h size: 32 bits function level reset: no bit description 31:24 port arbitration table offset ? ro. hardwire d to 0 since this field is not valid for endpoint devices. 23 reserved. 22:16 maximum time slots ? ro. hardwired to 0 si nce this field is not valid for endpoint devices. 15 reject snoop transactions ? ro. hardwired to 0 since this field is not valid for endpoint devices. 14 advanced packet switching ? ro. hardwired to 0 since this field is not valid for endpoint devices. 13:8 reserved 7:0 port arbitration capability ? ro. hardwired to 0 since this field is not valid for endpoint devices. bit description 31 vci enable ? r/w. 0 = vci is disabled 1 = vci is enabled note: this bit is not reset on d3 hot to d0 transition; however, it is reset by pltrst#. 30:27 reserved. 26:24 vci id ? r/w. this field assigns a vc id to th e vci resource. this field is not used by the ich10 hardware, but it is r/w to avoid confusing software. 23:20 reserved. 19:17 port arbitration select ? ro. hardwired to 0 since this field is not valid for endpoint devices. 16 load port arbitration table ? ro. hardwired to 0 since this field is not valid for endpoint devices. 15:8 reserved. 7:0 tc/vci map ? r/w, ro. this field indicates the tcs that are mapped to the vci resource. bit 0 is hardwired to 0 indicating th at it cannot be mapped to vci. bits [7:1] are implemented as r/w bits. th is field is not used by the ich10 hardware, but it is r/w to avoid confusing software. http://www..net/ datasheet pdf - http://www..net/ datasheet 673 intel ? high definition audio controller registers (d27:f0) 18.1.44 vcists?vci resource status register (intel ? high definition au dio controller?d27:f0) address offset: 126h-127h attribute: ro default value: 0000h size: 16 bits 18.1.45 rccap?root complex link declaration enhanced capability header register (intel ? high definition audio controller?d27:f0) address offset: 130h attribute: ro default value: 00010005h size: 32 bits 18.1.46 esd?element self description register (intel ? high definition au dio controller?d27:f0) address offset: 134h-137h attribute: ro default value: 0f000100h size: 32 bits bit description 15:2 reserved. 1 vci negotiation pending ? ro. does not apply. hardwired to 0. 0 port arbitration table status ? ro. hardwire d to 0 since this field is not valid for endpoint devices. bit description 31:20 next capability offset ? ro. hardwired to 0 indicating this is the last capability. 19:16 capability version ? ro. hardwired to 1h. 15:0 pci express* extended capability id ? ro. hardwired to 0005h. bit description 31:24 port number ? ro. hardwired to 0fh indicating that the intel ? high definition audio controller is assigned as port #15d. 23:16 component id ? ro. this field returns the value of the esd.cid field of the chip configuration section. esd.cid is programmed by bios. 15:8 number of link entries ? ro. the intel high definition audio only connects to one device, the ich10 egress port. therefore this field reports a value of 1h. 7:4 reserved. 3:0 element type (eltyp ) ? ro. the intel high definition audio controller is an integrated root complex de vice. therefore, the fiel d reports a value of 0h. http://www..net/ datasheet pdf - http://www..net/ intel ? high definition audio controller registers (d27:f0) 674 datasheet 18.1.47 l1desc?link 1 description register (intel ? high definition audio controller?d27:f0) address offset: 140h-143h attribute: ro default value: 00000001h size: 32 bits 18.1.48 l1addl?link 1 lo wer address register (intel ? high definition audio controller?d27:f0) address offset: 148h-14bh attribute: ro default value: see register description size: 32 bits 18.1.49 l1addu?link 1 u pper address register (intel ? high definition audio controller?d27:f0) address offset: 14ch-14fh attribute: ro default value: 00000000h size: 32 bits bit description 31:24 target port number ? ro. the intel high definition audio controller targets the intel ? ich10?s port 0. 23:16 target component id ? ro. this field returns the value of the esd.cid field of the chip configuration section. esd.cid is programmed by bios. 15:2 reserved. 1 link type ? ro. hardwired to 0 indicating type 0. 0 link valid ? ro. hardwired to 1. bit description 31:14 link 1 lower address ? ro. hardwired to match the rcba register value in the pci- lpc bridge (d31:f0:f0h). 13:0 reserved. bit description 31:0 link 1 upper address ? ro. hardwired to 00000000h. http://www..net/ datasheet pdf - http://www..net/ datasheet 675 intel ? high definition audio controller registers (d27:f0) 18.2 intel ? high definition audio memory mapped configuration registers (intel ? high definition audio? d27:f0) the base memory location for these memory mapped configuration registers is specified in the hdbar register (d27:f0:offset 10h and d27:f0:offset 14h). the individual registers are then accessible at hdbar + offset as indicated in ta b l e 1 8 . 2 . these memory mapped registers must be accessed in byte, word, or dword quantities. table 18-2. intel ? high definition audio pci register address map (intel ? high definition audio d27:f0) (sheet 1 of 4) hdbar + offset mnemonic register name default access 00h?01h gcap global capabilities 4401h ro 02h vmin minor version 00h ro 03h vmaj major version 01h ro 04h?05h outpay output payload capability 003ch ro 06h?07h inpay input payload capability 001dh ro 08h?0bh gctl global control 00000000h r/w 0ch?0dh wakeen wake enable 0000h r/w 0eh?0fh statests state change status 0000h r/wc 10h?11h gsts global status 0000h r/wc 12h?13h rsv reserved 0000h ro 18h?19h outstrmpay output stream payload capability 0030h ro 1ah?1bh instrmpay input stream payload capability 0018h ro 1ch?1fh rsv reserved 00000000h ro 20h?23h intctl interrupt control 00000000h r/w 24h?27h intsts interrupt status 00000000h ro 30h?33h walclk wall clock counter 00000000h ro 34h?37h ssync stream synchronization 00000000h r/w 40h?43h corblbase corb lower base address 00000000h r/w, ro 44h?47h corbubase corb upper base address 00000000h r/w 48h?49h corbwp corb write pointer 0000h r/w 4ah?4bh corbrp corb read pointer 0000h r/w, ro 4ch corbctl corb control 00h r/w 4dh corbst corb status 00h r/wc 4eh corbsize corb size 42h ro 50h?53h rirblbase rirb lower base address 00000000h r/w, ro 54h?57h rirbubase rirb upper base address 00000000h r/w 58h?59h rirbwp rirb write pointer 0000h r/w, ro 5ah?5bh rintcnt response interrupt count 0000h r/w 5ch rirbctl rirb control 00h r/w http://www..net/ datasheet pdf - http://www..net/ intel ? high definition audio controller registers (d27:f0) 676 datasheet 5dh rirbsts rirb status 00h r/wc 5eh rirbsize rirb size 42h ro 60h?63h ic immediate command 00000000h r/w 64h?67h ir immediate response 00000000h ro 68h?69h irs immediate command status 0000h r/w, r/ wc 70h?73h dplbase dma position lower base address 00000000h r/w, ro 74h?77h dpubase dma position upper base address 00000000h r/w 80?82h isd0ctl input stream descriptor 0 (isd0) control 040000h r/w, ro 83h isd0sts isd0 status 00h r/wc, ro 84h?87h isd0lpib isd0 link position in buffer 00000000h ro 88h?8bh isd0cbl isd0 cyclic buffer length 00000000h r/w 8ch?8dh isd0lvi isd0 last valid index 0000h r/w 8eh?8f isd0fifow isd0 fifo watermark 0004h r/w 90h?91h isd0fifos isd0 fifo size 0077h ro 92h?93h isd0fmt isd0 format 0000h r/w 98h?9bh isd0bdpl isd0 buffer descript or list pointer- lower base address 00000000h r/w, ro 9ch?9fh isd0bdpu isd0 buffer descript ion list pointer- upper base address 00000000h r/w a0h?a2h isd1ctl input stream descriptor 1(isd01) control 040000h r/w, ro a3h isd1sts isd1 status 00h r/wc, ro a4h?a7h isd1lpib isd1 link position in buffer 00000000h ro a8h?abh isd1cbl isd1 cyclic buffer length 00000000h r/w ach?adh isd1lvi isd1 last valid index 0000h r/w aeh?afh isd1fifow isd1 fifo watermark 0004h r/w b0h?b1h isd1fifos isd1 fifo size 0077h ro b2h?b3h isd1fmt isd1 format 0000h r/w b8h?bbh isd1bdpl isd1 buffer descript or list pointer- lower base address 00000000h r/w, ro bch?bfh isd1bdpu isd1 buffer descript ion list pointer- upper base address 00000000h r/w c0h?c2h isd2ctl input stream descriptor 2 (isd2) control 040000h r/w, ro c3h isd2sts isd2 status 00h r/wc, ro c4h?c7h isd2lpib isd2 link position in buffer 00000000h ro c8h?cbh isd2cbl isd2 cyclic buffer length 00000000h r/w table 18-2. intel ? high definition audio pci register address map (intel ? high definition audio d27:f0) (sheet 2 of 4) hdbar + offset mnemonic register name default access http://www..net/ datasheet pdf - http://www..net/ datasheet 677 intel ? high definition audio controller registers (d27:f0) cch?cdh isd2lvi isd2 last valid index 0000h r/w ceh?cfh isd1fifow isd1 fifo watermark 0004h r/w d0h?d1h isd2fifos isd2 fifo size 0077h ro d2h?d3h isd2fmt isd2 format 0000h r/w d8h?dbh isd2bdpl isd2 buffer descriptor list pointer- lower base address 00000000h r/w, ro dch?dfh isd2bdpu isd2 buffer descripti on list pointer- upper base address 00000000h r/w e0h?e2h isd3ctl input stream descriptor 3 (isd3) control 040000h r/w, ro e3h isd3sts isd3 status 00h r/wc, ro e4h?e7h isd3lpib isd3 link position in buffer 00000000h ro e8h?ebh isd3cbl isd3 cyclic buffer length 00000000h r/w ech?edh isd3lvi isd3 last valid index 0000h r/w eeh?efh isd3fifow isd3 fifo watermark 0004h r/w f0h?f1h isd3fifos isd3 fifo size 0077h ro f2h?f3h isd3fmt isd3 format 0000h r/w f8h?fbh isd3bdpl isd3 buffer descriptor list pointer- lower base address 00000000h r/w, ro fch?ffh isd3bdpu isd3 buffer descripti on list pointer- upper base address 00000000h r/w 100h?102h osd0ctl output stream desc riptor 0 (osd0) control 040000h r/w, ro 103h osd0sts osd0 status 00h r/wc, ro 104h?107h osd0lpib osd0 link position in buffer 00000000h ro 108h?10bh osd0cbl osd0 cyclic buffer length 00000000h r/w 10ch?10dh osd0lvi osd0 last valid index 0000h r/w 10eh?10fh osd0fifow osd0 fifo watermark 0004h r/w 110h?111h osd0fifos osd0 fifo size 00bfh r/w 112?113h osd0fmt osd0 format 0000h r/w 118h?11bh osd0bdpl osd0 buffer descript or list pointer- lower base address 00000000h r/w, ro 11ch?11fh osd0bdpu osd0 buffer descript ion list pointer- upper base address 00000000h r/w 120h?122h osd1ctl output stream desc riptor 1 (osd1) control 040000h r/w, ro 123h osd1sts osd1 status 00h r/wc, ro 124h?127h osd1lpib osd1 link position in buffer 00000000h ro 128h?12bh osd1cbl osd1 cyclic buffer length 00000000h r/w table 18-2. intel ? high definition audio pci register address map (intel ? high definition audio d27:f0) (sheet 3 of 4) hdbar + offset mnemonic register name default access http://www..net/ datasheet pdf - http://www..net/ intel ? high definition audio controller registers (d27:f0) 678 datasheet 12ch?12dh osd1lvi osd1 last valid index 0000h r/w 12eh?12fh osd1fifow osd1 fifo watermark 0004h r/w 130h?131h osd1fifos osd1 fifo size 00bfh r/w 132h?133h osd1fmt osd1 format 0000h r/w 138h?13bh osd1bdpl osd1 buffer descriptor list pointer- lower base address 00000000h r/w, ro 13ch?13fh osd1bdpu osd1 buffer description list pointer- upper base address 00000000h r/w 140h?142h osd2ctl output stream descriptor 2 (osd2) control 040000h r/w, ro 143h osd2sts osd2 status 00h r/wc, ro 144h?147h osd2lpib osd2 link position in buffer 00000000h ro 148h?14bh osd2cbl osd2 cyclic buffer length 00000000h r/w 14ch?14dh osd2lvi osd2 last valid index 0000h r/w 14eh?14fh osd2fifow osd2 fifo watermark 0004h r/w 150h?151h osd2fifos osd2 fifo size 00bfh r/w 152h?153h osd2fmt osd2 format 0000h r/w 158h?15bh osd2bdpl osd2 buffer descriptor list pointer- lower base address 00000000h r/w, ro 15ch?15fh osd2bdpu osd2 buffer description list pointer- upper base address 00000000h r/w 160h?162h osd3ctl output stream descriptor 3 (osd3) control 040000h r/w, ro 163h osd3sts osd3 status 00h r/wc, ro 164h?167h osd3lpib osd3 link position in buffer 00000000h ro 168h?16bh osd3cbl osd3 cyclic buffer length 00000000h r/w 16ch?16dh osd3lvi osd3 last valid index 0000h r/w 16eh?16fh osd3fifow osd3 fifo watermark 0004h r/w 170h?171h osd3fifos osd3 fifo size 00bfh r/w 172h?173h osd3fmt osd3 format 0000h r/w 178h?17bh osd3bdpl osd3 buffer descriptor list pointer- lower base address 00000000h r/w, ro 17ch?17fh osd3bdpu osd3 buffer description list pointer- upper base address 00000000h r/w table 18-2. intel ? high definition audio pci register address map (intel ? high definition audio d27:f0) (sheet 4 of 4) hdbar + offset mnemonic register name default access http://www..net/ datasheet pdf - http://www..net/ datasheet 679 intel ? high definition audio controller registers (d27:f0) 18.2.1 gcap?global capa bilities register (intel ? high definition au dio controller?d27:f0) memory address:hdbar + 00h attribute: ro default value: 4401h size: 16 bits 18.2.2 vmin?minor version register (intel ? high definition au dio controller?d27:f0) memory address:hdbar + 02h attribute: ro default value: 00h size: 8 bits 18.2.3 vmaj?major version register (intel ? high definition au dio controller?d27:f0) memory address:hdbar + 03h attribute: ro default value: 01h size: 8 bits bit description 15:12 number of output stream supported ? ro. hardwired to 0100b indicating that the ich10 intel ? high definition audio contro ller supports 4 output streams. 11:8 number of input stream supported ? ro. hardwired to 0100b indicating that the ich10 intel high definition audio controller supports 4 input streams. 7:3 number of bidirectional stream supported ? ro. hardwired to 0 indicating that the ich10 intel high definition audio co ntroller supports 0 bi directional stream. 2 reserved. 1 number of serial data out signals ? ro. hardwired to 0 indicating that the ich10 intel high definition audio controller supports 1 serial data output signal. 0 64-bit address supported ? ro. hardwired to 1b indicating that the ich10 intel high definition audio controller supports 64-bit addressing for bdl addresses, data buffer addressees, and co mmand buffer addresses. bit description 7:0 minor version ? ro. hardwired to 0 indicating that the intel ? ich10 supports minor revision number 00h of the intel ? high definition audio specification. bit description 7:0 major version ? ro. hardwired to 01h indicating that the intel ? ich10 supports major revision number 1 of the intel ? high definition audio specification. http://www..net/ datasheet pdf - http://www..net/ intel ? high definition audio controller registers (d27:f0) 680 datasheet 18.2.4 outpay?output payl oad capability register (intel ? high definition audio controller?d27:f0) memory address:hdbar + 04h attribute: ro default value: 003ch size: 16 bits 18.2.5 inpay?input payloa d capability register (intel ? high definition audio controller?d27:f0) memory address:hdbar + 06h attribute: ro default value: 001dh size: 16 bits bit description 15:7 reserved. 6:0 output payload capability ? ro. hardwired to 3ch indicating 60 word payload. this field indicates the total output payload available on the link. this does not include bandwidth used for command and control. this measurement is in 16-bit word quantities per 48 mhz fr ame. the default link clock of 24.000 mhz (the data is double pumped) provides 1000 bits pe r frame, or 62.5 words in total. 40 bits are used for command and control, leaving 60 words available for data payload. 00h = 0 word 01h = 1 word payload. ..... ffh = 256 word payload. bit description 15:7 reserved. 6:0 input payload capability ? ro. hardwired to 1dh indicating 29 word payload. this field indicates the total output payload available on the link. this does not include bandwidth used for response. this measurement is in 16-b it word quantities per 48 mhz frame. the default link clock of 24.000 mhz provides 500 bits per frame, or 31.25 words in total. 36 bits are used for resp onse, leaving 29 words available for data payload. 00h = 0 word 01h = 1 word payload. ..... ffh = 256 word payload. http://www..net/ datasheet pdf - http://www..net/ datasheet 681 intel ? high definition audio controller registers (d27:f0) 18.2.6 gctl?global control register (intel ? high definition au dio controller?d27:f0) memory address:hdbar + 08h attribute: r/w default value: 00000000h size: 32 bits bit description 31:9 reserved. 8 accept unsolicited response enable ? r/w. 0 = unsolicited responses from the codecs are not accepted. 1 = unsolicited response from the codecs are ac cepted by the controll er and placed into the response input ring buffer. 7:2 reserved. 1 flush control ? r/w. writing a 1 to this bit initiates a flush. when the flush completion is received by the controller, ha rdware sets the flush status bit and clears this flush control bit. before a flush cycle is initiated, the dma position buffer must be programmed with a valid memory address by software, but the dma position buffer bit 0 needs not be set to enable the position reporting mechanism. also, all streams must be stopped (the associat ed run bit must be 0). when the flush is initiated, the controller wi ll flush the pipelines to memory to ensure that the hardware is ready to transition to a d3 state. setting this bit is not a critical step in the power state transition if the content of the fifos is not critical. 0 controller reset # ? r/w. 0 = writing a 0 causes the inte l high definition audio contro ller to be re set. all state machines, fifos and non-resume well memory mapped configuration registers (not pci configuration registers) in the co ntroller will be re set. the intel high definition audio link reset# signal will be asserted, and all other link signals will be driven to their default values. after the hardware has completed sequencing into the reset state, it will report a 0 in this bit. software must read a 0 from this bit to verify the controller is in reset. 1 = writing a 1 causes the controller to exit its reset state and deassert the intel high definition audio link reset# signal. soft ware is responsible for setting/clearing this bit such that the minimum intel high definition audio link reset# signal assertion pulse width specification is met. when the controller ha rdware is ready to begin operation, it will report a 1 in this bit. software must read a 1 from this bit before accessing any controll er registers. this bit defa ults to a 0 after hardware reset, therefore, software needs to write a 1 to this bit to begin operation. notes: 1. the corb/rirb run bits and all stream ru n bits must be verified cleared to 0 before writing a 0 to this bit in order to assure a clean re-start. 2. when setting or clearing this bit, softwa re must ensure that minimum link timing requirements (minimum reset# assertion time, etc.) are met. 3. when this bit is 0 indicating that the controller is in re set, writes to all intel high definition audio memory ma pped registers are ignored as if the device is not present. the only exception is this register itself. the global control register is write-able as a dword, word, or byte even when crst# (this bit) is 0 if the byte enable for the byte containi ng the crst# bit (byte enable 0) is active. if byte enable 0 is not active, writes to the glob al control register will be ignored when crst# is 0. when crst# is 0, reads to intel high definition audio memory mapped registers will return their default value except for registers that are not reset with pltrst# or on a d3 hot to d0 transition. http://www..net/ datasheet pdf - http://www..net/ intel ? high definition audio controller registers (d27:f0) 682 datasheet 18.2.7 wakeen?wake enable register (intel ? high definition audio controller?d27:f0) memory address: hdbar + 0ch attribute: r/w default value: 0000h size: 16 bits function level reset: no 18.2.8 statests?state change status register (intel ? high definition audio controller?d27:f0) memory address: hdbar + 0eh attribute: r/wc default value: 0000h size: 16 bits function level reset: no bit description 15:4 reserved. 3:0 sdin wake enable flags ? r/w. these bits control which sdi signal(s) may generate a wake event. a 1b in the bit mask indicates that the associ ated sdin signal is enabled to generate a wake. bit 0 is used for sdi[0] bit 1 is used for sdi[1] bit 2 is used for sdi[2] bit 3 is used for sdi[3] note: these bits are in the resume well an d only cleared on a power on reset. software must not make assumptions ab out the reset state of these bits and must set them appropriately. bit description 15:4 reserved. 3:0 sdin state change status flags ? r/wc. flag bits that in dicate which sdi signal(s) received a state change event. the bits are cleared by writing 1s to them. bit 0 = sdi[0] bit 1 = sdi[1] bit 2 = sdi[2] bit 3 = sdi[3] note: these bits are in the resume well an d only cleared on a power on reset. software must not make assumptions ab out the reset state of these bits and must set them appropriately. http://www..net/ datasheet pdf - http://www..net/ datasheet 683 intel ? high definition audio controller registers (d27:f0) 18.2.9 gsts?global status register (intel ? high definition au dio controller?d27:f0) memory address: hdbar + 10h attribute: r/wc default value: 0000h size: 16 bits 18.2.10 outstrmpay?output st ream payload capability (intel ? high definition au dio controller?d27:f0) memory address: hdbar + 18h attribute: ro default value: 0030h size: 16 bits bit description 15:4 reserved. 3 reserved 2 reserved 1 flush status ? r/wc. this bit is set to 1 by hardware to indicate that the flush cycle initiated when the flush control bit (hdb ar + 08h, bit 1) was set has completed. software must write a 1 to clear this bit be fore the next time th e flush control bit is set to clear the bit. 0 reserved. bit description 15:14 output fifo padding type (opadtype) ? ro: indicates how the controller pads the samples in the controller's buffer (fifo) . controllers may not pad at all or may pad to byte or memory container sizes. 0h =controller pads all samples to bytes 1h = reserved 2h = controller pads to memory container size 3h = controller does not pa d and uses samples directly 13:0 output stream payload capability (outstrmpay) ? ro : indicates maximum number of words per frame for any single outp ut stream. this measur ement is in 16 bit word quantities per 48 khz frame. 48 words (96b) is the maximum supported, therefore a value of 30h is reported in this register. the value does not specify the number of words actually transmitted in the frame, but is the size of the data in the controller buffer (fifo) after the samples are padded as specified by opadtype. thus to compute the supported streams, each sa mple is padded according to opadtype and then multiplied by the number of channels and samples per frame. if this computed value is larger than outstrmpay then that stream is not supported. the value specified is not affected by striping. software must ensure that a format which would ca use more words per frame than indicated is not programmed into the output stream descriptor register. the value may be larger than the outpay register value in some cases. http://www..net/ datasheet pdf - http://www..net/ intel ? high definition audio controller registers (d27:f0) 684 datasheet 18.2.11 instrmpay?input st ream payload capability (intel ? high definition audio controller?d27:f0) memory address:hdbar + 1ah attribute: ro default value: 0018h size: 16 bits bit description 15:14 input fifo padding type (ipadtype) ? ro. indicates how the controller pads the samples in the controller's buffer (fifo). co ntrollers may not pad at all or may pad to byte or memory container sizes. 0h = controller pads all samples to bytes 1h = reserved 2h = controller pads to memory container size 3h = controller does not pa d and uses sa mples directly 13:0 input stream payload capability (instrmpay) ? ro. indicates the maximum number of words per frame for any single inpu t stream. this measurement is in 16-bit word quantities per 48-kh z frame. 24 words (48b) is the maximum supported, therefore a value of 18h is reported in this register. the value does not specify the number of words actually transmitted in the frame, but is the size of the data as it will be plac ed into the controller 's buffer (fifo). thus samples will be padded according to ipadty pe before being stored into controller buffer. to compute the suppo rted streams, each sample is padded according to ipadtype and then multiplied by the number of channels and samples per frame. if this computed value is larger than instrmpay th en that stream is not supported. as the inbound stream tag is not stored with the sa mples it is not included in the word count. the value may be larger than inpay register value in some cases, although values less than inpay may also be invalid due to overhe ad. software must ensure that a format which would cause more words per frame th an indicated is not programmed into the input stream descriptor register. http://www..net/ datasheet pdf - http://www..net/ datasheet 685 intel ? high definition audio controller registers (d27:f0) 18.2.12 intctl?interrupt control register (intel ? high definition au dio controller?d27:f0) memory address:hdbar + 20h attribute: r/w default value: 00000000h size: 32 bits bit description 31 global interrupt enable (gie) ? r/w. global bit to en able device interrupt generation. 1 = when set to 1, the intel ? high definition audio function is enabled to generate an interrupt. this control is in addition to an y bits in the bus spec ific address space, such as the interrupt enable bi t in the pci configuration space. note: this bit is not affected by the d3 hot to d0 transition. 30 controller interrupt enable (cie) ? r/w. enables the general interrupt for controller functions. 1 = when set to 1, the controller generates an interrupt when the corresponding status bit gets set due to a response interrupt , a response buffer overrun, and state change events. note: this bit is not affected by the d3 hot to d0 transition. 29:8 reserved 7:0 stream interrupt enable (sie) ? r/w. when set to 1, th e individual streams are enabled to generate an in terrupt when the correspondi ng status bits get set. a stream interrupt will be caused as a resu lt of a buffer with ioc = 1in the bdl entry being completed, or as a result of a fifo error (underrun or ove rrun) occurring. control over the generation of each of these source s is in the associated stream descriptor. the streams are numbered and the sie bits as signed sequentially, based on their order in the register set. bit 0 = input stream 1 bit 1 = input stream 2 bit 2 = input stream 3 bit 3 = input stream 4 bit 4 = output stream 1 bit 5 = output stream 2 bit 6 = output stream 3 bit 7 = output stream 4 http://www..net/ datasheet pdf - http://www..net/ intel ? high definition audio controller registers (d27:f0) 686 datasheet 18.2.13 intsts?interrupt status register (intel ? high definition audio controller?d27:f0) memory address:hdbar + 24h attribute: ro default value: 00000000h size: 32 bits 18.2.14 walclk?wall cloc k counter register (intel ? high definition audio controller?d27:f0) memory address:hdbar + 30h attribute: ro default value: 00000000h size: 32 bits bit description 31 global interrupt status (gis) ? ro. this bit is an or of all the interrupt status bits in this register. note: this bit is not affected by the d3 hot to d0 transition. 30 controller interrupt status (cis) ? ro. status of genera l controller interrupt. 1 = interrupt condition occurred due to a response interrupt, a response buffer overrun interrupt, or a sdin state ch ange event. the exact cause can be determined by interrogating other registers. this bit is an or of all of the stated interrupt status bits for this register. notes: 1. this bit is set regardless of the state of the corresponding interrupt enable bit, but a hardware interrupt will not be ge nerated unless the corresponding enable bit is set. 2. this bit is not affected by the d3 hot to d0 transition. 29:8 reserved 7:0 stream interrup t status (sis) ? ro. 1 = interrupt condition occurred on the corresponding stream. th is bit is an or of all of the stream?s interrupt status bits. note: these bits are set regardless of the stat e of the corresponding interrupt enable bits. the streams are numbered and the sie bits a ssigned sequentially, based on their order in the register set. bit 0 = input stream 1 bit 1 = input stream 2 bit 2 = input stream 3 bit 3 = input stream 4 bit 4 = output stream 1 bit 5 = output stream 2 bit 6 = output stream 3 bit 7 = output stream 4 bit description 31:0 wall clock counter ? ro. 32 bit counter that is in cremented on each link bit clock period and rolls over from ffff ffffh to 0000 0000h. this counter will roll over to 0 with a period of approximately 179 seconds. this counter is enabled while the bit clock bit is set to 1. software uses this counter to synchronize between multiple controllers. will be reset on controller reset. http://www..net/ datasheet pdf - http://www..net/ datasheet 687 intel ? high definition audio controller registers (d27:f0) 18.2.15 ssync?stream synchronization register (intel ? high definition au dio controller?d27:f0) memory address:hdbar + 34h attribute: r/w default value: 00000000h size: 32 bits 18.2.16 corblbase?corb lower base address register (intel ? high definition au dio controller?d27:f0) memory address:hdbar + 40h attribute: r/w, ro default value: 00000000h size: 32 bits bit description 31:8 reserved 7:0 stream synchronization (ssync) ? r/w. when set to 1, these bits block data from being sent on or received from the link. each bit controls the associated stream descriptor (i.e. bit 0 corresponds to the first stream descriptor, etc.) to synchronously start a set of dma engines, these bits are first set to 1. the run bits for the associated stream descriptors are then set to 1 to start the dma engines. when all streams are ready (fifordy =1), the associated ssync bits can all be set to 0 at the same time, and transmission or receptio n of bits to or from the link will begin together at the start of the next full link frame. to synchronously stop the streams, fist these bits are set, and then the individual run bits in the stream descripto r are cleared by software. if synchronization is not desired, these bits ma y be left as 0, and th e stream will simply begin running normally when the stream?s run bit is set. the streams are numbered and the sie bits as signed sequentially, based on their order in the register set. bit 0 = input stream 1 bit 1 = input stream 2 bit 2 = input stream 3 bit 3 = input stream 4 bit 4 = output stream 1 bit description 31:7 corb lower base address ? r/w. lower address of the command output ring buffer, allowing the corb base address to be assigned on any 128-b boundary. this register field must not be wr itten when the dma engine is running or the dma transfer may be corrupted. 6:0 corb lower base unimplemented bits ? ro. hardwired to 0. this required the corb to be allocated with 128b granularity to allow for cache line fetch optimizations. http://www..net/ datasheet pdf - http://www..net/ intel ? high definition audio controller registers (d27:f0) 688 datasheet 18.2.17 corbubase?corb uppe r base address register (intel ? high definition audio controller?d27:f0) memory address:hdbar + 44h attribute: r/w default value: 00000000h size: 32 bits 18.2.18 corbwp?corb write pointer register (intel ? high definition audio controller?d27:f0) memory address:hdbar + 48h attribute: r/w default value: 0000h size: 16 bits 18.2.19 corbrp?corb read pointer register (intel ? high definition audio controller?d27:f0) memory address:hdbar + 4ah attribute: r/w, ro default value: 0000h size: 16 bits bit description 31:0 corb upper base address ? r/w. upper 32 bits of the address of the command output ring buffer. this register field mu st not be written when the dma engine is running or the dma transfer may be corrupted. bit description 15:8 reserved. 7:0 corb write pointer ? r/w. software writes the last valid corb entry offset into this field in dword granularity. the dma engine fetches commands from the corb until the read pointer matches the write pointer. supports 256 corb entries (256x4b = 1 kb). this register field may be writte n when the dma engine is running. bit description 15 corb read pointer reset ? r/w. software writes a 1 to this bit to reset the corb read pointer to 0 and clear any residual prefetched commands in the corb hardware buffer within the intel ? high definition audio controller. the hardware will physically update this bit to 1 when the corb pointer reset is complete. soft ware must read a 1 to verify that the reset completed correctly. software must clear this bit back to 0 and read back the 0 to verify that the clea r completed correctly. the corb dma engine must be stopped prior to re setting the read pointer or else dma transfer may be corrupted. 14:8 reserved. 7:0 corb read pointer (corbrp) ? ro. software reads this field to determine how many commands it can write to the corb without over-running. the value read indicates the corb read pointer offset in dw ord granularity. the offset entry read from this field has been successfully fetched by the dma controller and may be over-written by software. supports 256 corb entries (256 x 4b=1kb). this field may be read while the dma engine is running. http://www..net/ datasheet pdf - http://www..net/ datasheet 689 intel ? high definition audio controller registers (d27:f0) 18.2.20 corbctl?corb control register (intel ? high definition au dio controller?d27:f0) memory address:hdbar + 4ch attribute: r/w default value: 00h size: 8 bits 18.2.21 corbst?corb status register (intel ? high definition au dio controller?d27:f0) memory address:hdbar + 4dh attribute: r/wc default value: 00h size: 8 bits 18.2.22 corbsize?corb size register intel ? high definition audio controller?d27:f0) memory address:hdbar + 4eh attribute: ro default value: 42h size: 8 bits bit description 7:2 reserved. 1 enable corb dma engine ? r/w. 0 = dma stop 1 = dma run after software writes a 0 to this bit, th e hardware may not stop immediately. the hardware will physically upda te the bit to 0 when the dma engine is truly stopped. software must read a 0 from th is bit to verify that the dma engine is truly stopped. 0 corb memory error interrupt enable ? r/w. if this bit is set the controller will generate an interrupt if the cmei status bit (hdbar + 4dh: bit 0) is set. bit description 7:1 reserved. 0 corb memory error indication (cmei) ? r/wc. 1 = controller detected an er ror in the path way between the controller and memory. this may be an ecc bit error or any othe r type of detectable data error which renders the command data fetched invalid. software can clear this bit by writing a 1 to it. however, this type of error leaves the audio subsystem in an un-via ble state and typica lly required a controller reset by writing a 0 to the controller re set # bit (hdbar + 08h: bit 0). bit description 7:4 corb size capability ? ro. hardwired to 0100b indicating that the ich10 only supports a corb size of 256 corb entries (1024b) 3:2 reserved. 1:0 corb size ? ro. hardwired to 10b which sets th e corb size to 256 entries (1024b) http://www..net/ datasheet pdf - http://www..net/ intel ? high definition audio controller registers (d27:f0) 690 datasheet 18.2.23 rirblbase?rirb lower base address register (intel ? high definition audio controller?d27:f0) memory address:hdbar + 50h attribute: r/w, ro default value: 00000000h size: 32 bits 18.2.24 rirbubase?rirb upper base address register (intel ? high definition audio controller?d27:f0) memory address:hdbar + 54h attribute: r/w default value: 00000000h size: 32 bits 18.2.25 rirbwp?rirb writ e pointer register (intel ? high definition audio controller?d27:f0) memory address:hdbar + 58h attribute: r/w, ro default value: 0000h size: 16 bits bit description 31:7 corb lower base address ? r/w. lower address of the response input ring buffer, allowing the rirb base address to be assigned on an y 128-b boundary. this register field must not be written when the dma engine is running or the dma transfer may be corrupted. 6:0 rirb lower base unimplemented bits ? ro. ha rdwired to 0. this required the rirb to be allocated with 128-b granularity to allow for cache line fetch optimizations. bit description 31:0 rirb upper base address ? r/w. upper 32 bits of th e address of the response input ring buffer. this regi ster field must not be writ ten when the dma engine is running or the dma transfer may be corrupted. bit description 15 rirb write pointer reset ? r/w. software writes a 1 to this bit to reset the rirb write pointer to 0. the rirb dma engine mu st be stopped prior to resetting the write pointer or else dma transfer may be corrupted. this bit is always read as 0. 14:8 reserved. 7:0 rirb write pointer (rirbwp) ? ro. indicates the last valid rirb entry written by the dma controller. software reads this fiel d to determine how ma ny responses it can read from the rirb. the value read indicates the rirb write pointer offset in 2 dword rirb entry units (since each rirb entry is 2 dwords long). supports up to 256 rirb entries (256 x 8 b = 2 kb). this register field may be written when the dma engine is running. http://www..net/ datasheet pdf - http://www..net/ datasheet 691 intel ? high definition audio controller registers (d27:f0) 18.2.26 rintcnt?response in terrupt count register (intel ? high definition au dio controller?d27:f0) memory address:hdbar + 5ah attribute: r/w default value: 0000h size: 16 bits 18.2.27 rirbctl?rirb control register (intel ? high definition au dio controller?d27:f0) memory address:hdbar + 5ch attribute: r/w default value: 00h size: 8 bits bit description 15:8 reserved. 7:0 n response interrupt count ? r/w. 0000 0001b = 1 response sent to rirb ........... 1111 1111b = 255 responses sent to rirb 0000 0000b = 256 responses sent to rirb the dma engine should be sto pped when changing this field or else an interrupt may be lost. note that each response occu pies 2 dwords in the rirb. this is compared to the total number of responses that have been returned, as opposed to the number of frames in which there we re responses. if mo re than one codecs responds in one frame, then the count is increased by the number of responses received in the frame. bit description 7:3 reserved. 2 response overrun interrupt control ? r/w. if this bit is set, the hardware will generate an interrupt when the response overrun interrupt status bit (hdbar + 5dh: bit 2) is set. 1 enable rirb dma engine ? r/w. 0 = dma stop 1 = dma run after software writes a 0 to this bit, th e hardware may not stop immediately. the hardware will physically upda te the bit to 0 when the dma engine is truly stopped. software must read a 0 from th is bit to verify that the dma engine is truly stopped. 0 response interrupt control ? r/w. 0 = disable interrupt 1 = generate an interrupt after n number of responses are sent to the rirb buffer or when an empty response slot is encoun tered on all sdi[x] inputs (whichever occurs first). the n coun ter is reset when the interrupt is generated. http://www..net/ datasheet pdf - http://www..net/ intel ? high definition audio controller registers (d27:f0) 692 datasheet 18.2.28 rirbsts?rirb status register (intel ? high definition audio controller?d27:f0) memory address:hdbar + 5dh attribute: r/wc default value: 00h size: 8 bits 18.2.29 rirbsize?rirb size register (intel ? high definition audio controller?d27:f0) memory address:hdbar + 5eh attribute: ro default value: 42h size: 8 bits 18.2.30 ic?immediate command register (intel ? high definition audio controller?d27:f0) memory address:hdbar + 60h attribute: r/w default value: 00000000h size: 32 bits bit description 7:3 reserved. 2 response overrun interrupt status ? r/wc. 1 = software sets this bit to 1 when the rirb dma engine is not able to write the incoming responses to memory before a dditional incoming re sponses overrun the internal fifo. when the overrun occurs, the hardware will drop the responses which overrun the buffer. an interrupt may be generate d if the response overrun interrupt control bit is set. note that this status bit is set even if an interrupt is not enabled for this event. software clears this bit by writing a 1 to it. 1 reserved. 0 response interrupt ? r/wc. 1 = hardware sets this bit to 1 when an interrupt has been generated after n number of responses are sent to the rirb buffe r or when an empty response slot is encountered on all sdi[x] inputs (whichever occurs fi rst). note that this status bit is set even if an interrupt is not enabled for this event. software clears this bit by writing a 1 to it. bit description 7:4 rirb size capability ? ro. hardwired to 0100b indicating that the ich10 only supports a rirb size of 256 rirb entries (2048b) 3:2 reserved. 1:0 rirb size ? ro. hardwired to 10b which sets the corb size to 256 entries (2048b) bit description 31:0 immediate command write ? r/w . the command to be sent to the codec via the immediate command mechanism is written to this register. the command stored in this register is sent out over the link during the next available frame after a 1 is written to the icb bit (hdbar + 68h: bit 0) http://www..net/ datasheet pdf - http://www..net/ datasheet 693 intel ? high definition audio controller registers (d27:f0) 18.2.31 ir?immediate response register (intel ? high definition au dio controller?d27:f0) memory address:hdbar + 64h attribute: ro default value: 00000000h size: 32 bits 18.2.32 irs?immediate comm and status register (intel ? high definition au dio controller?d27:f0) memory address:hdbar + 68h attribute: r/w, r/wc default value: 0000h size: 16 bits bit description 31:0 immediate response read (irr) ? ro. this register contains the response received from a codec resulting from a command sent via the immediate command mechanism. if multiple codecs responded in the same time, there is no assurance as to which response will be latched. th erefore, broadcast-type comman ds must not be issued via the immediate command mechanism. bit description 15:2 reserved. 1 immediate result valid (irv) ? r/wc. 1 = set to 1 by hardware when a new response is latched into the immediate response register (hdbar + 64). this is a status flag indicating that software may read the response from the immedi ate response register. software must clear th is bit by writing a 1 to it befo re issuing a new command so that the software may dete rmine when a new response has arrived. 0 immediate command busy (icb) ? r/w. when this bit is read as 0, it indicates that a new command may be issued using the im mediate command mech anism. when this bit transitions from a 0 to a 1 (via software writing a 1), the controller issues the command currently stored in the immediate command register to the codec over the link. when the corresponding response is latched into the immediate response register, the controller hardware sets the irv fl ag and clears the icb bit back to 0. note: an immediate command must not be issued while the corb/rirb mechanism is operating, otherwise the responses conflict. this must be enforced by software. http://www..net/ datasheet pdf - http://www..net/ intel ? high definition audio controller registers (d27:f0) 694 datasheet 18.2.33 dplbase?dma position lo wer base address register (intel ? high definition audio controller?d27:f0) memory address:hdbar + 70h attribute: r/w, ro default value: 00000000h size: 32 bits 18.2.34 dpubase?dma position u pper base addr ess register (intel ? high definition audio controller?d27:f0) memory address:hdbar + 74h attribute: r/w default value: 00000000h size: 32 bits bit description 31:7 dma position lowe r base address ? r/w. lower 32 bits of the dma position buffer base address. this register field must not be written when any dma engine is running or the dma transfer may be corrupted. this same address is used by the flush control and must be programmed with a vali d value before the flush control bit (hdbar+08h:bit 1) is set. 6:1 dma position lower base unim plemented bits ? ro. hardwired to 0 to force the 128- byte buffer alignment for cache line write optimizations. 0 dma position buffer enable ? r/w. 1 = controller will write the dma positions of each of the dma engines to the buffer in the main memory periodically (typically once per frame). software can use this value to know what data in memory is valid data. bit description 31:0 dma position upper base address ? r/w. upper 32 bits of the dma position buffer base address. this register field must not be written when any dma engine is running or the dma transfer may be corrupted. http://www..net/ datasheet pdf - http://www..net/ datasheet 695 intel ? high definition audio controller registers (d27:f0) 18.2.35 sdctl?stream descri ptor control register (intel ? high definition au dio controller?d27:f0) memory address:input stream[0]: hdbar + 80h attribute: r/w, ro input stream[1]: hdbar + a0h input stream[2]: hdbar + c0h input stream[3]: hdbar + e0h output stream[0]: hdbar + 100h output stream[1]: hdbar + 120h output stream[2]: hdbar + 140h output stream[3]: hdbar + 160h default value: 040000h size: 24 bits bit description 23:20 stream number ? r/w. this value reflect the tag associated with the data being transferred on the link. when data controlled by this de scriptor is sent out over the link, it will have its stream number encoded on the sync signal. when an input stream is dete cted on any of the sdi signals that match this value, the data samples are loaded into fifo associated with this descriptor. note that while a single sdi input may contain data from more than one stream number, two different sdi inputs may not be configured with the same stream number. 0000 = reserved 0001 = stream 1 ........ 1110 = stream 14 1111 = stream 15 19 bidirectional direction control ? ro. this bit is only meaningful for bidirectional streams; therefore, this bit is hardwired to 0. 18 traffic priority ? ro. hardwired to 1 indicating that all streams will use vc1 if it is enabled through the pci express* registers. 17:16 stripe control ? ro. this bit is only meaningf ul for input streams; th erefore, this bit is hardwired to 0. 15:5 reserved 4 descriptor error interrupt enable ? r/w. 0 = disable 1 = an interrupt is generated when th e descriptor error status bit is set. 3 fifo error interrupt enable ? r/w. this bit controls whether the occurrence of a fifo error (overrun for input or underrun for output) will cause an interrupt or not. if this bit is not set, bit 3in the status register will be set, but the interrupt will not occur. either way, the samples will be dropped. 2 interrupt on completion enable ? r/w. this bit controls whether or not an interrupt occurs when a buffer completes with the ioc bi t set in its descriptor. if this bit is not set, bit 2 in the status re gister will be set, but the interrupt will not occur. http://www..net/ datasheet pdf - http://www..net/ intel ? high definition audio controller registers (d27:f0) 696 datasheet 1 stream run (run) ? r/w. 0 = dma engine associated with this input st ream will be disabled. the hardware will report a 0 in this bit when the dma engine is actually stopped. software must read a 0 from this bit before modifying relate d control registers or restarting the dma engine. 1 = dma engine associated with this input st ream will be enabled to transfer data from the fifo to the main memory. the ssync bi t must also be cleared in order for the dma engine to run. for outp ut streams, the cadence ge nerator is reset whenever the run bit is set. 0 stream reset (srst) ? r/w. 0 = writing a 0 causes the corresponding st ream to exit reset. when the stream hardware is ready to begin operation, it wi ll report a 0 in this bit. software must read a 0 from this bit before acce ssing any of the stream registers. 1 = writing a 1 causes the corresponding stre am to be reset. th e stream descriptor registers (except the srst bit itself) and fifo?s for the corresponding stream are reset. after the stream hard ware has completed sequencing into the reset state, it will report a 1 in this bit. software must read a 1 from this bit to verify that the stream is in reset. the run bit must be cleared be fore srst is asserted. bit description http://www..net/ datasheet pdf - http://www..net/ datasheet 697 intel ? high definition audio controller registers (d27:f0) 18.2.36 sdsts?stream descri ptor status register (intel ? high definition au dio controller?d27:f0) memory address:input stream[0]: hdbar + 83h attribute:r/wc, ro input stream[1]: hdbar + a3h input stream[2]: hdbar + c3h input stream[3]: hdbar + e3h output stream[0]: hdbar + 103h output stream[1]: hdbar + 123h output stream[2]: hdbar + 143h output stream[3]: hdbar + 163h default value: 00h size: 8 bits bit description 7:6 reserved. 5 fifo ready (fifordy) ? ro. for output streams, the controller hardware will set this bit to 1 while the output dma fifo contains enough data to maintain the stream on the link. this bit defaults to 0 on rese t because the fifo is cleared on a reset. for input streams, the controller hardware wi ll set this bit to 1 when a valid descriptor is loaded and the engine is re ady for the run bit to be set. 4 descriptor error ? r/wc. 1 = a serious error occurred duri ng the fetch of a descriptor. this could be a result of a master abort, a parity or ecc error on the bus, or any othe r error which renders the current buffe r descriptor or buffer de scriptor list useless. this error is treated as a fatal stream error, as the stream ca nnot continue running. the run bit will be cleared and the stre am will stopped. software may attempt to restart the stream engine afte r addressing the cause of the error and writing a 1 to this bit to clear it. 3 fifo error ? r/wc. 1 = fifo error occurred. this bit is set even if an interrupt is no t enabled. the bit is cleared by writing a 1 to it. for an input stream, this indi cates a fifo overrun occurring while the run bit is set. when this happens, the fifo pointers do no t increment and the incoming data is not written into the fifo, thereby being lost. for an output stream, this in dicates a fifo underrun when there are still buffers to send. the hardware should not transmit anythi ng on the link for the associated stream if there is not valid data to send. 2 buffer completion interrupt status ? r/wc. this bit is set to 1 by the hardware after the last sample of a buffer has be en processed, and if the interrupt on completion bit is set in the command byte of the buffer descriptor . it remains active until software clears it by writing a 1 to it. 1:0 reserved. http://www..net/ datasheet pdf - http://www..net/ intel ? high definition audio controller registers (d27:f0) 698 datasheet 18.2.37 sdlpib?stream descriptor link position in buffer register (intel ? high definition audio controller?d27:f0) memory address:input stream[0]: hdbar + 84h attribute:ro input stream[1]: hdbar + a4h input stream[2]: hdbar + c4h input stream[3]: hdbar + e4h output stream[0]: hdbar + 104h output stream[1]: hdbar + 124h output stream[2]: hdbar + 144h output stream[3]: hdbar + 164h default value: 00000000h size: 32 bits 18.2.38 sdcbl?stream descriptor cy clic buffer length register (intel ? high definition audio controller?d27:f0) memory address:input stream[0]: hdbar + 88h attribute:r/w input stream[1]: hdbar + a8h input stream[2]: hdbar + c8h input stream[3]: hdbar + e8h output stream[0]: hdbar + 108h output stream[1]: hdbar + 128h output stream[2]: hdbar + 148h output stream[3]: hdbar + 168h default value: 00000000h size: 32 bits bit description 31:0 link position in buffer ? ro. indicates the number of bytes that have been received off the link. this register will count from 0 to the value in the cyclic buffer length register and then wrap to 0. bit description 31:0 cyclic buffer length ? r/w. indicates the number of bytes in the complete cyclic buffer. this register represen ts an integer number of samp les. link position in buffer will be reset when it reaches this value. software may only write to this register afte r global reset, controll er reset, or stream reset has occurred. this value should be only modified when the run bit is 0. once the run bit has been set to enable the engine, software must not write to this register until after the next reset is asserted , or transfer may be corrupted. http://www..net/ datasheet pdf - http://www..net/ datasheet 699 intel ? high definition audio controller registers (d27:f0) 18.2.39 sdlvi?stream descriptor last valid index register (intel ? high definition au dio controller?d27:f0) memory address:input stream[0]: hdbar + 8ch attribute: r/w input stream[1]: hdbar + ach input stream[2]: hdbar + cch input stream[3]: hdbar + ech output stream[0]: hdbar + 10ch output stream[1]: hdbar + 12ch output stream[2]: hdbar + 14ch output stream[3]: hdbar + 16ch default value: 0000h size: 16 bits 18.2.40 sdfifow?stream descript or fifo watermark register (intel ? high definition au dio controller?d27:f0) memory address:input stream[0]: hdbar + 8eh attribute: r/w input stream[1]: hdbar + aeh input stream[2]: hdbar + ceh input stream[3]: hdbar + eeh output stream[0]: hdbar + 10eh output stream[1]: hdbar + 12eh output stream[2]: hdbar + 14eh output stream[3]: hdbar + 16eh default value: 0004h size: 16 bits bit description 15:8 reserved. 7:0 last valid index ? r/w. the value written to this re gister indicates the index for the last valid buffer descriptor in bdl. after the controller has processe d this desc riptor, it will wrap back to the first descriptor in the list and continue processing. this field must be at least 1, i.e. there must be at leas t 2 valid entries in the buffer descriptor list before dma operations can begin. this value should only modified when the run bit is 0. bit description 15:3 reserved. 2:0 fifo watermark (fifow) ? r/w. indicates the minimum number of bytes accumulated/free in the fifo be fore the controller will star t a fetch/eviction of data. 010 = 8b 011 = 16b 100 = 32b (default) 101 = 64b others = unsupported note: when the bit field is prog rammed to an unsupported size, the hardware sets itself to the default value. software must read the bit fi eld to test if the value is supported after setting the bit field. http://www..net/ datasheet pdf - http://www..net/ intel ? high definition audio controller registers (d27:f0) 700 datasheet 18.2.41 sdfifos?stream descri ptor fifo si ze register (intel ? high definition audio controller?d27:f0) memory address:input stream[0]: hdbar + 90hattribute: input: ro input stream[1]: hdbar + b0houtput: r/w input stream[2]: hdbar + d0h input stream[3]: hdbar + f0h output stream[0]: hdbar + 110h output stream[1]: hdbar + 130h output stream[2]: hdbar + 150h output stream[3]: hdbar + 170h default value: input stream: 0077h size: 16 bits output stream: see description. bit description 15:10 reserved. 9:0 fifo size ? ro (input stream), r/w (outpu t stream). indicates the maximum number of bytes that could be fetched by the controller at one time. this is the maximum number of bytes that may have been dma?d into memory but not yet transmitted on the link, and is also the maximum possible value that the picb count will increase by at one time. the value in this field is different for input and output streams. it is also dependent on the bits per samples setting for the corresp onding stream. following are the values read/written from/to this register for in put and output streams, and for non-padded and padded bit formats: output stream r/w value : notes: 1. all other values not listed are not supported. 2. when the output stream is programmed to an unsuppo rted size, the hardware sets itself to the default value (bfh). 3. software must read the bit field to test if the value is supported after setting the bit field. input stream ro value : note: the default value is different for input and output streams, and reflects the default state of the bits fi elds (in stream descriptor format registers) for the corresponding stream. value output streams 0fh = 16b 8, 16, 20, 24, or 32 bit output streams 1fh = 32b 8, 16, 20, 24, or 32 bit output streams 3fh = 64b 8, 16, 20, 24, or 32 bit output streams 7fh = 128b 8, 16, 20, 24, or 32 bit output streams bfh = 192b 8, 16, or 32 bit output streams (default) ffh = 256b 20 or 24 bit output streams (default) 17fh = 384b 8, 16, or 32 bit output streams 1ffh = 512b 20 or 24 bit output streams value input streams 77h = 120b 8, 16, 32 bit input streams 9fh = 160b 20, 24 bit input streams http://www..net/ datasheet pdf - http://www..net/ datasheet 701 intel ? high definition audio controller registers (d27:f0) 18.2.42 sdfmt?stream descriptor format register (intel ? high definition au dio controller?d27:f0) memory address:input stream[0]: hdbar + 92h attribute:r/w input stream[1]: hdbar + b2h input stream[2]: hdbar + d2h input stream[3]: hdbar + f2h output stream[0]: hdbar + 112h output stream[1]: hdbar + 132h output stream[2]: hdbar + 152h output stream[3]: hdbar + 172h default value: 0000h size: 16 bits bit description 15 reserved. 14 sample base rate ? r/w 0 = 48 khz 1 = 44.1 khz 13:11 sample base rate multiple ? r/w 000 = 48 khz, 44.1 khz or less 001 = x2 (96 khz, 88.2 khz, 32 khz) 010 = x3 (144 khz) 011 = x4 (192 khz, 176.4 khz) others = reserved. 10:8 sample base rate devisor ? r/w. 000 = divide by 1(48 khz, 44.1 khz) 001 = divide by 2 (24 khz, 22.05 khz) 010 = divide by 3 (16 khz, 32 khz) 011 = divide by 4 (11.025 khz) 100 = divide by 5 (9.6 khz) 101 = divide by 6 (8 khz) 110 = divide by 7 111 = divide by 8 (6 khz) 7 reserved. 6:4 bits per sample (bits) ? r/w. 000 = 8 bits. the data will be packed in memory in 8-bit containers on 16-bit boundaries 001 = 16 bits. the data will be packed in memory in 16-bit co ntainers on 16-bit boundaries 010 = 20 bits. the data will be packed in memory in 32-bit containers on 32-bit boundaries 011 = 24 bits. the data will be packed in memory in 32-bit co ntainers on 32-bit boundaries 100 = 32 bits. the data will be packed in memory in 32-bit co ntainers on 32-bit boundaries others = reserved. 3:0 number of channels (chan) ? r/w. indicates number of channels in each frame of the stream. 0000 =1 0001 =2 ........ 1111 =16 http://www..net/ datasheet pdf - http://www..net/ intel ? high definition audio controller registers (d27:f0) 702 datasheet 18.2.43 sdbdpl?stream descriptor buffer descriptor list pointer lower base address register (intel ? high definition audio controller?d27:f0) memory address:input stream[0]: hdbar + 98h attribute: r/w,ro input stream[1]: hdbar + b8h input stream[2]: hdbar + d8h input stream[3]: hdbar + f8h output stream[0]: hdbar + 118h output stream[1]: hdbar + 138h output stream[2]: hdbar + 158h output stream[3]: hdbar + 178h default value: 00000000h size: 32 bits 18.2.44 sdbdpu?stream descriptor buffer descriptor list pointer upper base address register (intel ? high definition audio controller?d27:f0) memory address:input stream [0]: hdbar + 9ch attribute: r/w input stream[1]: hdbar + bch input stream[2]: hdbar + dch input stream[3]: hdbar + fch output stream[0]: hdbar + 11ch output stream[1]: hdbar + 13ch output stream[2]: hdbar + 15ch output stream[3]: hdbar + 17ch default value: 00000000h size: 32 bits bit description 31:7 buffer descriptor list po inter lower base address ? r/w. lower address of the buffer descriptor list. this valu e should only be modified when the run bit is 0, or dma transfer may be corrupted. 6:0 hardwired to 0 forcing alignment on 128-b boundaries. bit description 31:0 buffer descriptor list pointer upper base address ? r/w. upper 32-bit address of the buffer descriptor list. th is value should only be modified when the run bit is 0, or dma transfer may be corrupted. http://www..net/ datasheet pdf - http://www..net/ datasheet 703 smbus controller registers (d31:f3) 19 smbus controller registers (d31:f3) 19.1 pci configuration registers (smbus?d31:f3) note: registers that are not shown should be treated as reserved (see section 9.2 for details). 19.1.1 vid?vendor identificati on register (smbus?d31:f3) address: 00h ? 01h attribute: ro default value: 8086h size: 16 bits table 19-1. smbus controller pci re gister address map (smbus?d31:f3) offset mnemonic register name default type 00h?01h vid vendor identification 8086 ro 02h?03h did device identification see register description ro 04h?05h pcicmd pci command 0000h r/w, ro 06h?07h pcists pci status 0280h ro 08h rid revision identification see register description ro 09h pi programming interface 00h ro 0ah scc sub class code 05h ro 0bh bcc base class code 0ch ro 10h smbmbar0 memory base address register 0 (bit 31:0) 00000004h r/w 14h smbmbar1 memory based address register 1 (bit 63:32) 00000000h r/w 20h?23h smb_base smbus base address 00000001h r/w, ro 2ch?2dh svid subsystem vendor identification 0000h ro 2eh?2fh sid subsystem identification 0000h r/wo 3ch int_ln interrupt line 00h r/w 3dh int_pn interrupt pin see register description ro 40h hostc host configuration 00h r/w bit description 15:0 vendor id ? ro. this is a 16-bit value assigned to intel http://www..net/ datasheet pdf - http://www..net/ smbus controller registers (d31:f3) 704 datasheet 19.1.2 did?device identificati on register (smbus?d31:f3) address: 02h ? 03h attribute: ro default value: see bit description size: 16 bits 19.1.3 pcicmd?pci command register (smbus?d31:f3) address: 04h ? 05h attributes: ro, r/w default value: 0000h size: 16 bits bit description 15:0 device id ? ro. this is a 16-bit value assigned to the intel? ich10 smbus controller. refer to the intel ? i/o controller hub (ich10) family specification update for the value of the device id register. bit description 15:11 reserved 10 interrupt disable ? r/w. 0 = enable 1 = disables smbus to assert its pirqb# signal. 9 fast back to back enable (fbe) ? ro. hardwired to 0. 8 serr# enable (serr_en) ? r/w. 0 = enables serr# generation. 1 = disables serr# generation. 7 wait cycle control (wcc) ? ro. hardwired to 0. 6 parity error response (per) ? r/w. 0 = disable 1 = sets detected parity error bit (d31:f3:06 , bit 15) when a parity error is detected. 5 vga palette snoop (vps) ? ro. hardwired to 0. 4 postable memory write enable (pmwe) ? ro. hardwired to 0. 3 special cycle en able (sce) ? ro. hardwired to 0. 2 bus master enable (bme) ? ro. hardwired to 0. 1 memory space enable (mse) ? r/w. 0 = disables memory mapped config space. 1 = enables memory mapped config space. 0 i/o space enable (iose) ? r/w. 0 = disable 1 = enables access to the smbus i/o space registers as defined by the base address register. http://www..net/ datasheet pdf - http://www..net/ datasheet 705 smbus controller registers (d31:f3) 19.1.4 pcists?pci status register (smbus?d31:f3) address: 06h ? 07h attributes: ro default value: 0280h size: 16 bits note: for the writable bits, software must write a 1 to clear bits that are set. writing a 0 to the bit has no effect. 19.1.5 rid?revision identificati on register (smbus?d31:f3) offset address: 08h attribute: ro default value: see bit description size: 8 bits bit description 15 detected parity error (dpe) ? r/wc. 0 = no parity error detected. 1 = parity error detected. 14 signaled system error (sse) ? r/wc. 0 = no system error detected. 1 = system error detected. 13 received master abort (rma) ? ro. hardwired to 0. 12 received target abort (rta) ? ro. hardwired to 0. 11 signaled target abort (sta) ? ro. hardwired to 0. 10:9 devsel# timing status (devt) ? ro. this 2-bit field defines the timing for devsel# assertion for positive decode. 01 = medium timing. 8 data parity error detected (d ped) ? ro. hardwired to 0. 7 fast back to back capable (fb2bc) ? ro. hardwired to 1. 6 user definable features (udf) ? ro. hardwired to 0. 5 66 mhz capable (66mhz_cap) ? ro. hardwired to 0. 4 capabilities list (cap_list) ? ro. hardwired to 0 because there are no capability list structures in this function 3 interrupt status (ints) ? ro. this bit indicates that an interrupt is pe nding. it is independent from the state of the interrupt enable bit in the pci command register. 2:0 reserved bit description 7:0 revision id ? ro. refer to the intel ? i/o controller hub (ich10) family specification update for the value of the revision id register. http://www..net/ datasheet pdf - http://www..net/ smbus controller registers (d31:f3) 706 datasheet 19.1.6 pi?programming interfac e register (smbus?d31:f3) offset address: 09h attribute: ro default value: 00h size: 8 bits 19.1.7 scc?sub class code register (smbus?d31:f3) address offset: 0ah attributes: ro default value: 05h size: 8 bits 19.1.8 bcc?base class code register (smbus?d31:f3) address offset: 0bh attributes: ro default value: 0ch size: 8 bits 19.1.9 smbmbar0?d31_f3_smbus memory base address 0 (smbus?d31:f3) address offset: 10-13h attributes: r/w, ro default value: 00000004h size: 32 bits bit description 7:0 reserved bit description 7:0 sub class code (scc) ? ro. 05h = smbus serial controller bit description 7:0 base class code (bcc) ? ro. 0ch = serial controller. bit description 31:8 base address ? r/w. provides the 32 byte system memory base address for the intel ich10 smb logic. 7:4 reserved 3 prefetchable (pref) ? ro. hardwired to 0. indicates that smbmbar is not pre- fetchable. 2:1 address range (addrng) ? ro. indicates that this smbmbar can be located anywhere in 64 bit address space. hardwired to 10b. 0 memory space indicator ? ro. this read-only bit always is 0, indicating that the smb logic is memory mapped. http://www..net/ datasheet pdf - http://www..net/ datasheet 707 smbus controller registers (d31:f3) 19.1.10 smbmbar1?d31_f3_smbus memory base address 1 (smbus?d31:f3) address offset: 14h-17h attributes: r/w default value: 00000000h size: 32 bits 19.1.11 smb_base?smbus ba se address register (smbus?d31:f3) address offset: 20 ? 23h attribute: r/w, ro default value: 00000001h size: 32-bits 19.1.12 svid?subsystem vendor identification register (smbus?d31:f2/f4) address offset: 2ch ? 2dh attribute: ro default value: 0000h size: 16 bits lockable: no power well: core bit description 31:0 base address ? r/w. provides bits 63-32 system memory base address for the intel ich10 smb logic. bit description 31:16 reserved ? ro 15:5 base address ? r/w. this field provides the 32-b yte system i/o base address for the ich10 smb logic. 4:1 reserved ? ro 0 io space indicator ? ro. hardwired to 1 in dicating that the smb logic is i/o mapped. bit description 15:0 subsystem vendor id (svid) ? ro. the svid register, in combination with the subsystem id (sid) register, enables the operating system (os) to distinguish subsystems from each other. the value returned by reads to this register is the same as that which was written by bios into the ide svid register. note: software can write to this register only once per core well re set. writes should be done as a single 16-bit cycle. http://www..net/ datasheet pdf - http://www..net/ smbus controller registers (d31:f3) 708 datasheet 19.1.13 sid?subsystem identification register (smbus?d31:f2/f4) address offset: 2eh ? 2fh attribute: r/wo default value: 0000h size: 16 bits lockable: no power well: core 19.1.14 int_ln?interrupt line register (smbus?d31:f3) address offset: 3ch attributes: r/w default value: 00h size: 8 bits 19.1.15 int_pn?interrupt pin register (smbus?d31:f3) address offset: 3dh attributes: ro default value: see description size: 8 bits bit description 15:0 subsystem id (sid) ? r/wo. the sid register, in combination with the svid register, enables the operating system (os) to distinguish subsystems from each other. the value returned by reads to this register is the same as that which was written by bios into the ide sid register. note: software can write to this register only once per core well re set. writes should be done as a single 16-bit cycle. bit description 7:0 interrupt line (int_ln) ? r/w. this data is not used by the ich10. it is to communicate to software the interrupt line that the interrupt pin is connected to pirqb#. bit description 7:0 interrupt pin (int_pn) ? ro. this reflects the valu e of d31ip.smip in chipset configuration space. http://www..net/ datasheet pdf - http://www..net/ datasheet 709 smbus controller registers (d31:f3) 19.1.16 hostc?host configurat ion register (smbus?d31:f3) address offset: 40h attribute: r/w default value: 00h size: 8 bits bit description 7:4 reserved 3 ssreset - soft smbus reset ? r/w. 0 = the hw will reset this bit to 0 wh en smbus reset operation is completed. 1 = the smbus state machine and logic in ich10 is reset. 2 i 2 c_en ? r/w. 0 = smbus behavior. 1 = the ich10 is enabled to communicate with i 2 c devices. this will change the formatting of some commands. 1 smb_smi_en ? r/w. 0 = smbus interrupts will not generate an smi#. 1 = any source of an smb interrupt will inst ead be routed to gene rate an smi#. refer to section 5.20.4 (interrupts / smi#). this bit needs to be set fo r smbalert# to be enabled. 0 smbus host enable (hst_en) ? r/w. 0 = disable the smbus host controller. 1 = enable. the smb host cont roller interface is enable d to execute commands. the intren bit (offset smbase + 02h, bit 0) needs to be enabled for the smb host controller to interrupt or smi#. note that the smb host controller will not respond to any new requests until all inte rrupt requests have been cleared. http://www..net/ datasheet pdf - http://www..net/ smbus controller registers (d31:f3) 710 datasheet 19.2 smbus i/o and memory mapped i/o registers the following smbus registers can be accessed through i/o bar or memory bar registers in pci configuration space. the of fsets are the same for both i/o and memory mapped i/o registers. table 19-2. smbus i/o and memory mapped i/o register address map smb_base + offset mnemonic register name default type 00h hst_sts host status 00h r/wc, ro 02h hst_cnt host control 00h r/w, wo 03h hst_cmd host command 00h r/w 04h xmit_slva transmit slave address 00h r/w 05h hst_d0 host data 0 00h r/w 06h hst_d1 host data 1 00h r/w 07h host_block_db host block data byte 00h r/w 08h pec packet error check 00h r/w 09h rcv_slva receive slave address 44h r/w 0ah?0bh slv_data receive slave data 0000h ro 0ch aux_sts auxiliary status 00h r/wc, ro 0dh aux_ctl auxiliary control 00h r/w 0eh smlink_pin_ctl smlink pin control (tco compatible mode) see register description r/w, ro 0fh smbus_pin_ctl smbus pin control see register description r/w, ro 10h slv_sts slave status 00h r/wc 11h slv_cmd slave command 00h r/w 14h notify_daddr notify device address 00h ro 16h notify_dlow notify data low byte 00h ro 17h notify_dhigh notify data high byte 00h ro http://www..net/ datasheet pdf - http://www..net/ datasheet 711 smbus controller registers (d31:f3) 19.2.1 hst_sts?host status register (smbus?d31:f3) register offset: smbase + 00h attribute: r/wc, ro default value: 00h size: 8-bits all status bits are set by hardware and cleared by the software writing a one to the particular bit position. writing a 0 to any bit position has no effect. bit description 7 byte done status (ds) ? r/wc. 0 = software can clear this by writing a 1 to it. 1 = host controller received a byte (for bl ock read commands) or if it has completed transmission of a byte (for block write commands) when the 32- byte buffer is not being used. note that this bit will be set, even on the last byte of the transfer. this bit is not set when transmission is due to the lan interface heartbeat. this bit has no meaning for block transf ers when the 32-byte buffer is enabled. note: when the last byte of a block message is received, the host controller will set this bit. however, it will not immediately set the intr bit (bit 1 in this register). when the interrupt handle r clears the ds bit, the message is considered complete, and the host controller will then set the intr bit (and generate another interrupt). thus, for a block message of n bytes, the ich10 will generate n+1 interrupts. the interrupt handler need s to be implemented to handle these cases. when not using the 32 byte buffer, hardware will drive the smbclk signal low when the ds bit is set until sw clears the bit. this includes the last byte of a transfer. software must clear the ds bit before it can clear the busy bit. 6 inuse_sts ? r/w. this bit is used as se maphore among various independent software threads that may need to use th e ich10?s smbus logic, and has no other effect on hardware. 0 = after a full pci reset, a read to this bit returns a 0. 1 = after the first read, subseque nt reads will return a 1. a write of a 1 to this bit will reset the next read va lue to 0. writing a 0 to this bit has no effect. software can poll this bit until it reads a 0, and will then own the usage of the host controller. 5 smbalert_sts ? r/wc. 0 = interrupt or smi# was not generated by smbalert#. software clears this bit by writing a 1 to it. 1 = the source of the interrupt or smi# wa s the smbalert# signal. this bit is only cleared by software writing a 1 to the bit position or by rsmrst# going low. if the signal is programmed as a gp io, then this bit will never be set. 4 failed ? r/wc. 0 = software clears this bi t by writing a 1 to it. 1 = the source of the interrupt or smi# was a failed bus transaction. this bit is set in response to the kill bit being set to terminate the host transaction. 3 bus_err ? r/wc. 0 = software clears this bi t by writing a 1 to it. 1 = the source of the interrupt of smi# was a transaction collision. 2 dev_err ? r/wc. 0 = software clears this bit by writing a 1 to it. the ic h10 will then deassert the interrupt or smi#. 1 = the source of the interrupt or sm i# was due to one of the following: ? invalid command field, ? unclaimed cycle (host initiated), ?host device time-out error. http://www..net/ datasheet pdf - http://www..net/ smbus controller registers (d31:f3) 712 datasheet 19.2.2 hst_cnt?host control register (smbus?d31:f3) register offset: smbase + 02h attribute: r/w, wo default value: 00h size: 8-bits note: a read to this register will clear th e byte pointer of the 32-byte buffer. 1 intr ? r/wc. this bit can only be set by te rmination of a command. intr is not dependent on the intren bit (offset smbase + 02h, bit 0) of the host controller register (offset 02h). it is only dependent on the te rmination of the command. if the intren bit is not set, then the intr bit will be set, although the interrupt will not be generated. software can poll the intr bit in this non-interrupt case. 0 = software clears this bit by writing a 1 to it. the ich10 then deasserts the interrupt or smi#. 1 = the source of the interrupt or smi# was the successful completion of its last command. 0 host_busy ? r/wc. 0 = cleared by the ich10 when the current transaction is completed. 1 = indicates that the ich10 is running a command from the host interface. no smb registers should be accessed while this bit is set, except the block data byte register. the block data byte register can be accessed when th is bit is set only when the smb_cmd bits in the host cont rol register are programmed for block command or i 2 c read command. this is nece ssary in order to check the done_sts bit. bit description bit description 7 pec_en . ? r/w. 0 = smbus host controller does not perform the transa ction with the pec phase appended. 1 = causes the host controller to perform the smbus transaction with the packet error checking phase appended. for writes, the value of the pec byte is transferred from the pec register. for reads, the pec byte is loaded in to the pec register. this bit must be written prior to the write in which the start bit is set. 6 start ? wo. 0 = this bit will always return 0 on read s. the host_busy bit in the host status register (offset 00h) can be used to identify when the intel ? ich10 has finished the command. 1 = writing a 1 to this bit initiates the co mmand described in the smb_cmd field. all registers should be setup prior to writing a 1 to this bit position. 5 last_byte ? wo. this bit is used for block read commands. 1 = software sets this bit to indicate that the next byte will be the last byte to be received for the block. this causes the ich10 to send a nack (instead of an ack) after receiving the last byte. note: once the second_to_sts bit in tco 2_sts register (d31:f0, tcobase+6h, bit 1) is set, the last_byte bit also ge ts set. while the second_to_sts bit is set, the last_byte bit cannot be cl eared. this prevents the ich10 from running some of the smbus commands (block read/write, i 2 c read, block i 2 c write). http://www..net/ datasheet pdf - http://www..net/ datasheet 713 smbus controller registers (d31:f3) 4:2 smb_cmd ? r/w. the bit encoding below indica tes which command the ich10 is to perform. if enabled, the ich10 will generate an interrupt or smi# when the command has completed if the value is for a non-suppo rted or reserved command, the ich10 will set the device error (dev_err ) status bit (offset smbase + 00h, bit 2) and generate an interrupt when the start bit is set. th e ich10 will perform no command, and will not operate until dev_err is cleared. 000 = quick : the slave address and read/write value (bit 0) are stored in the transmit slave address register. 001 = byte : this command uses the transmit slave address and command registers. bit 0 of the slave address register determines if th is is a read or write command. 010 = byte data : this command uses the transmit slave address, command, and data0 registers. bit 0 of the slave address register determines if this is a read or write command. if it is a read, the da ta0 register will contain the read data. 011 = word data : this command uses the transmit slave address, command, data0 and data1 registers. bit 0 of the slave address register determines if this is a read or write command. if it is a read, after the command completes, the data0 and data1 registers wi ll contain the read data. 100 = process call: this command uses the transmit slave address, command, data0 and data1 registers. bit 0 of the slave address register determines if this is a read or write command. after the command completes, the data0 and data1 registers will contain the read data. 101 = block : this command uses the transmit slave address, command, data0 registers, and the block data byte regist er. for block write, the count is stored in the data0 register and indicates how ma ny bytes of data will be transferred. for block reads, the count is received an d stored in the data0 register. bit 0 of the slave address register selects if this is a read or write command. for writes, data is retrieved from the first n (where n is equal to the specified count) addresses of the sram array. for reads, the data is stored in the block data byte register. 110 = i 2 c read : this command uses the transmit slave address, command, data0, data1 registers, and the block data byte register. the read data is stored in the block data byte register. the ich10 continues reading data until the nak is received. 111 = block process: this command uses the transmit slave address, command, data0 and the block data byte register. fo r block write, the count is stored in the data0 register and indicates how many bytes of data will be transferred. for block read, the count is received and stored in the data0 register. bit 0 of the slave address register al ways indicate a write comm and. for writes, data is retrieved from the first m (where m is equal to the specified count) addresses of the sram array. for reads, the data is stored in the block data byte register. note: e32b bit in the auxiliary control register must be set for this command to work. 1 kill ? r/w. 0 = normal smbus host controller functionality. 1 = kills the current ho st transaction taking place, se ts the failed status bit, and asserts the interrupt (or smi#). this bit, once se t, must be cleare d by software to allow the smbus host controll er to function normally. 0 intren ? r/w. 0 = disable. 1 = enable the generation of an interrup t or smi# upon the completion of the command. bit description http://www..net/ datasheet pdf - http://www..net/ smbus controller registers (d31:f3) 714 datasheet 19.2.3 hst_cmd?host command register (smbus?d31:f3) register offset: smbase + 03h attribute: r/w default value: 00h size: 8 bits 19.2.4 xmit_slva?transmit slave address register (smbus?d31:f3) register offset: smbase + 04h attribute: r/w default value: 00h size: 8 bits this register is transmitted by the host co ntroller in the slave address field of the smbus protocol. 19.2.5 hst_d0?host data 0 register (smbus?d31:f3) register offset: smbase + 05h attribute: r/w default value: 00h size: 8 bits 19.2.6 hst_d1?host data 1 register (smbus?d31:f3) register offset: smbase + 06h attribute: r/w default value: 00h size: 8 bits bit description 7:0 this 8-bit field is transmitted by the host controller in the command field of the smbus protocol during the execution of any command. bit description 7:1 address ? r/w. this field provides a 7-bit address of the targeted slave. 0 rw ? r/w. direction of the host transfer. 0 = write 1 = read bit description 7:0 data0/count ? r/w. this field contains the 8-bit data sent in the data0 field of the smbus protocol. for block write commands, this register reflects the number of bytes to transfer. this register should be progra mmed to a value between 1 and 32 for block counts. a count of 0 or a count above 32 will result in unpredicta ble behavior. the host controller does not check or log invalid block counts. bit description 7:0 data1 ? r/w. this 8-bit register is transm itted in the data1 field of the smbus protocol during the execution of any command. http://www..net/ datasheet pdf - http://www..net/ datasheet 715 smbus controller registers (d31:f3) 19.2.7 host_block_db?host bl ock data byte register (smbus?d31:f3) register offset: smbase + 07h attribute: r/w default value: 00h size: 8 bits 19.2.8 pec?packet error check (pec) register (smbus?d31:f3) register offset: smbase + 08h attribute: r/w default value: 00h size: 8 bits bit description 7:0 block data (bdta) ? r/w. this is either a register, or a pointer into a 32-byte block array, depending upon whether the e32b bit is set in the auxiliary control register. when the e32b bit (offset smbase + 0dh, bit 1) is cleared, this is a register containing a byte of data to be sent on a block writ e or read from on a bl ock read, just as it behaved on the ich3. when the e32b bit is set, reads and writes to this register are us ed to access the 32- byte block data storage array. an internal index pointer is used to address the array, which is reset to 0 by readin g the hctl register (offset 02h). the index pointer then increments automatically upon each access to this register. the transfer of block data into (read) or out of (write) this storage array during an smbus transaction always starts at index address 0. when the e2b bit is set, for writes, software will write up to 32-bytes to this register as part of the setup for the co mmand. after the host controller has sent the address, command, and byte count fields, it will send the bytes in the sram pointed to by this register. when the e2b bit is cleared for writes, software will place a single by te in this register. after the host controller has sent the address, command, an d byte count fi elds, it will send the byte in this register. if there is more data to send, software will write the next series of bytes to the sram pointed to by th is register and clear the done_sts bit. the controller will then send th e next byte. during the time between the last byte being transmitted to the next byte being transmitted, the controller will insert wait-states on the interface. when the e2b bit is set for reads, after rece iving the byte count into the data0 register, the first series of data bytes go into the sr am pointed to by this register. if the byte count has been exhausted or the 32-byte sr am has been filled, the controller will generate an smi# or interrupt (depending on configuration) and set the done_sts bit. software will then read the data. during th e time between when the last byte is read from the sram to when the done_sts bit is cleared, the controller will insert wait- states on the interface. bit description 7:0 pec_data ? r/w. this 8-bit register is written with the 8-bit crc valu e that is used as the smbus pec data prior to a write transa ction. for read transactions, the pec data is loaded from the smbus into this register an d is then read by software. software must ensure that the inuse_sts bit is properly ma intained to avoid having this field over- written by a write transaction following a read transaction. http://www..net/ datasheet pdf - http://www..net/ smbus controller registers (d31:f3) 716 datasheet 19.2.9 rcv_slva?receive slave address register (smbus?d31:f3) register offset: smbase + 09h attribute: r/w default value: 44h size: 8 bits lockable: no power well: resume 19.2.10 slv_data?receive slave data register (smbus?d31:f3) register offset: smbase + 0ah?0bh attribute: ro default value: 0000h size: 16 bits lockable: no power well: resume this register contains the 16-bit data value written by the external smbus master. the processor can then read the value from this re gister. this register is reset by rsmrst#, but not pltrst# . 19.2.11 aux_sts?auxiliary stat us register (smbus?d31:f3) register offset: smbase + 0ch attribute: r/wc, ro default value: 00h size: 8 bits lockable: no power well: resume . bit description 7 reserved 6:0 slave_addr ? r/w. this field is the slave address that the intel ? ich10 decodes for read and write cycles. the de fault is not 0, so the smbu s slave interface can respond even before the processor comes up (or if the processor is dead). this register is cleared by rsmrst#, but not by pltrst#. bit description 15:8 data message byte 1 (data_msg1) ? ro. see section 5.20.7 for a discussion of this field. 7:0 data message byte 0 (data_msg0) ? ro. see section 5.20.7 for a discussion of this field. bit description 7:2 reserved 1 smbus tco mode (stco) ? ro. this bit reflects the st rap setting of tco compatible mode vs. advanced tco mode. 0 = intel ? ich10 is in the compatible tco mode. 1 = ich10 is in the advanced tco mode. 0 crc error (crce) ? r/wc. 0 = software clears this bit by writing a 1 to it. 1 = this bit is set if a received message contai ned a crc error. when this bit is set, the derr bit of the host status register will also be set. this bit will be set by the controller if a software abort occurs in th e middle of the crc portion of the cycle or an abort happens after the ich10 has receiv ed the final data bit transmitted by an external slave. http://www..net/ datasheet pdf - http://www..net/ datasheet 717 smbus controller registers (d31:f3) 19.2.12 aux_ctl?auxiliary cont rol register (smbus?d31:f3) register offset: smbase + 0dh attribute: r/w default value: 00h size: 8 bits lockable: no power well: resume . 19.2.13 smlink_pin_ctl?smlink pin control register (smbus?d31:f3) register offset: smbase + 0eh attribute: r/w, ro default value: see below size: 8 bits note: this register is in the resume well and is reset by rsmrst#. this register is only applicable in the tco compatible mode. bit description 7:2 reserved 1 enable 32-byte buffer (e32b) ? r/w. 0 = disable. 1 = enable. when set, the host block data register is a pointer into a 32-byte buffer, as opposed to a single re gister. this enables the block commands to transfer or receive up to 32-bytes before the ich10 generates an interrupt. 0 automatically append crc (aac) ? r/w. 0 = ich10 will not automatically append the crc. 1 = the ich10 will automatically append the crc. this bit must no t be changed during smbus transactions or undetermined behavior will result. it should be programmed only once during the li fetime of the function. bit description 7:3 reserved 2 smlink_clk_ctl ? r/w. 0 = ich10 will drive the smlink0 pin low, in dependent of what the other smlink logic would otherwise indicate for the smlink0 pin. 1 = the smlink0 pin is not overdriven low. the other smlink logic controls the state of the pin. (default) 1 smlink1_cur_sts ? ro. this read-only bit has a de fault value that is dependent on an external signal level. th is pin returns the value on th e smlink1 pin. this allows software to read the cu rrent state of the pin. 0 = low 1 = high 0 smlink0_cur_sts ? ro. this read-only bit has a de fault value that is dependent on an external signal level. th is pin returns the value on th e smlink0 pin. this allows software to read the cu rrent state of the pin. 0 = low 1 = high http://www..net/ datasheet pdf - http://www..net/ smbus controller registers (d31:f3) 718 datasheet 19.2.14 smbus_pin_ctl?smbus pin control register (smbus?d31:f3) register offset: smbase + 0fh attribute: r/w, ro default value: see below size: 8 bits note: this register is in the resume well and is reset by rsmrst#. 19.2.15 slv_sts?slave status register (smbus?d31:f3) register offset: smbase + 10h attribute: r/wc default value: 00h size: 8 bits note: this register is in the resume well and is reset by rsmrst#. all bits in this register are implemented in the 64 khz clock domain. therefore, software must poll this register until a write takes effect before assuming that a write has completed internally. bit description 7:3 reserved 2 smbclk_ctl ? r/w. 1 = the smbclk pin is not overdriven low. the other smbus logic controls the state of the pin. 0 = ich10 drives the smbclk pin low, indepe ndent of what the other smb logic would otherwise indicate for th e smbclk pin. (default) 1 smbdata_cur_sts ? ro. this read-only bit has a default value that is dependent on an external signal level. this pin returns the value on the smbdata pin. this allows software to read the cu rrent state of the pin. 0 = low 1 = high 0 smbclk_cur_sts ? ro. this read-only bit has a de fault value that is dependent on an external signal level. th is pin returns the value on th e smbclk pin. this allows software to read the cu rrent state of the pin. 0 = low 1 = high bit description 7:1 reserved 0 host_notify_sts ? r/wc. the ich10 sets this bit to a 1 when it has completely received a successful host notify command on the smlink (consumer only) or smbus pins (corporate only). softwa re reads this bit to determine that the source of the interrupt or smi# was the reception of the ho st notify command. software clears this bit after reading any information needed from the notify address and data registers by writing a 1 to this bit. note that the ic h10 will allow the noti fy address and data registers to be over-written once this bit has been cleared. when this bit is 1, the ich10 will nack the first byte (host address) of any new ?host notify? commands on the smlink (consumer only) or smbus pins (corporate only). writing a 0 to this bit has no effect. http://www..net/ datasheet pdf - http://www..net/ datasheet 719 smbus controller registers (d31:f3) 19.2.16 slv_cmd?slave comman d register (smbus?d31:f3) register offset: smbase + 11h attribute: r/w default value: 00h size: 8 bits note: this register is in the resume well and is reset by rsmrst#. 19.2.17 notify_daddr?notify device address register (smbus?d31:f3) register offset: smbase + 14h attribute: ro default value: 00h size: 8 bits note: this register is in the resume well and is reset by rsmrst#. bit description 7:2 reserved 2 smbalert_dis ? r/w. 0 = allows the generation of the interrupt or smi#. 1 = software sets this bit to block the generation of the interrupt or smi# due to the smbalert# source. this bit is logically inverted and anded with the smbalert_sts bit (offset smbase + 00h, bit 5). the resulting sign al is distributed to the smi# and/or interrupt generation logic. this bi t does not effect the wake logic. 1 host_notify_wken ? r/w. software sets this bit to 1 to enable the reception of a host notify command as a wake event. when enabled this event is ?or?d" in with the other smbus wake events an d is reflected in the smb_ wak_sts bit of the general purpose event 0 status register. 0 = disable 1 = enable 0 host_notify_intren ? r/w. software sets this bit to 1 to enable the generation of interrupt or smi# when host_notify_sts (offset smbase + 10h, bit 0) is 1. this enable does not affect the setting of the host_notify_sts bit. when the interrupt is generated, either pirqb# or smi# is ge nerated, depending on the value of the smb_smi_en bit (d31:f3:40h, bit 1). if the host_notify_sts bit is set when this bit is written to a 1, then the interrupt (or smi#) will be generated. the interrupt (or smi#) is logically generated by and?ing the sts and intren bits. 0 = disable 1 = enable bit description 7:1 device_address ? ro. this field contains the 7-bi t device address received during the host notify protocol of the smbus 2.0 sp ecification. software should only consider this field valid when the host_notify_sts bit (d31:f3:smbase +10, bit 0) is set to 1. 0 reserved http://www..net/ datasheet pdf - http://www..net/ smbus controller registers (d31:f3) 720 datasheet 19.2.18 notify_dlow?notify data low byte register (smbus?d31:f3) register offset: smbase + 16h attribute: ro default value: 00h size: 8 bits note: this register is in the resume well and is reset by rsmrst#. 19.2.19 notify_dhigh?notify data high byte register (smbus?d31:f3) register offset: smbase + 17h attribute: ro default value: 00h size: 8 bits note: this register is in the resume well and is reset by rsmrst#. bit description 7:0 data_low_byte ? ro. this field contains the firs t (low) byte of data received during the host notify protocol of the smbu s 2.0 specification. so ftware should only consider this field valid when the host_n otify_sts bit (d31:f3: smbase +10, bit 0) is set to 1. bit description 7:0 data_high_byte ? ro. this field contains the second (high) byte of data received during the host notify protocol of the smbu s 2.0 specification. software should only consider this field valid when the host_n otify_sts bit (d31:f3:smbase +10, bit 0) is set to 1. http://www..net/ datasheet pdf - http://www..net/ datasheet 721 pci express* configuration registers 20 pci express* configuration registers 20.1 pci express* configuration registers (pci express?d28:f0/f1/f2/f3/f4/f5) note: register address locations that are not shown in table 20-1 and should be treated as reserved. / table 20-1. pci express* configuration registers address map (pci express?d28:f0/f1/f2/f3/f4/f5) (sheet 1 of 3) offset mnemonic register name function 0?5 default type 00h?01h vid vendor identification 8086h ro 02h?03h did device identification see register description ro 04h?05h pcicmd pci command 0000h r/w, ro 06h?07h pcists pci status 0010h r/wc, ro 08h rid revision identification see register description ro 09h pi programming interface 00h ro 0ah scc sub class code 04h ro 0bh bcc base class code 06h ro 0ch cls cache line size 00h r/w 0dh plt primary latency timer 00h ro 0eh headtyp header type 81h ro 18h?1ah bnum bus number 000000h r/w 1bh slt secondary latency timer 00h ro 1ch?1dh iobl i/o base and limit 0000h r/w, ro 1eh?1fh ssts secondary status register 0000h r/wc 20h?23h mbl memory base and limit 00000000h r/w 24h?27h pmbl prefetchable memory base and limit 00010001h r/w, ro 28h?2bh pmbu32 prefetchable memory base upper 32 bits 00000000h r/w 2ch?2fh pmlu32 prefetchable memory limit upper 32 bits 00000000h r/w 34h capp capabilities list pointer 40h ro 3ch?3dh intr interru pt information see bit description r/w, ro 3eh?3fh bctrl bridge control register 0000h r/w 40h?41h clist capabilities list 8010 ro http://www..net/ datasheet pdf - http://www..net/ pci express* configuration registers 722 datasheet 42h?43h xcap pci express* capabilities 0041 r/wo, ro 44h?47h dcap device capabilities 00000fe0h ro 48h?49h dctl device control 0000h r/w, ro 4ah?4bh dsts device status 0010h r/wc, ro 4ch?4fh lcap link capabilities see bit description r/w, ro, r/wo 50h?51h lctl link control 0000h r/w, wo, ro 52h?53h lsts link status see bit description ro 54h?57h slcap slot capabilities register 00000060h r/wo, ro 58h?59h slctl slot control 0000h r/w, ro 5ah?5bh slsts slot status 0000h r/wc, ro 5ch?5dh rctl root control 0000h r/w 60h?63h rsts root status 00000000h r/wc, ro 64h-67h (corporate only) dcap2 device capabilities 2 register 00000016h ro 68h?69h (corporate only) dctl2 device control 2 register 0000h r/w, ro 70h?71h (corporate only) lctl2 link control 2 register 0001h ro 80h?81h mid message signal ed interrupt identifiers 9005h ro 82h?83h mc message signal ed interrupt message control 0000h r/w, ro 84h?87h ma message signal ed interrupt message address 00000000h r/w 88h?89h md message signal ed interrupt message data 0000h r/w 90h?91h svcap subsystem vendor capability a00dh ro 94h?97h svid subsystem vendor identification 00000000h r/wo a0h?a1h pmcap power management capability 0001h ro a2h?a3h pmc pci power management capability c802h ro a4?a7h pmcs pci power management control and status 00000000h r/w, ro d4-d7h mpc2 miscellaneous port configuration 2 00000000h r/w, ro d8?dbh mpc miscellaneous port configuration 08110000h r/w table 20-1. pci express* config uration registers address map (pci express?d28:f0/f1/f2/f3/f4/f5) (sheet 2 of 3) offset mnemonic register name function 0?5 default type http://www..net/ datasheet pdf - http://www..net/ datasheet 723 pci express* configuration registers dc?dfh smscs smi/sci status register 00000000h r/wc e1h rpdcgen rort port dynamic clock gating enable 00h r/w e8-ebh pecr1 pci express configuration register 1 00000020h r/w 100?103h vch virtual channel capability header 18010002h r/wo 104h?107h ? reserved ? ? 108h?10bh vcap2 virtual channel capability 2 00000001h ro 10ch?10dh pvc port virtual channel control 0000h r/w 10eh?10fh pvs port virtual channel status 0000h ro 110h?113h v0cap virtual channel 0 resource capability 00000001h ro 114?117h v0ctl virtual channel 0 resource control 800000ffh r/w, ro 11a?11bh v0sts virtual channel 0 resource status 0000h ro 11ch?143h ? reserved ? ? 144h?147h ues uncorrectable error status see bit description r/wc, ro 148h?14bh uem uncorrectable error mask 00000000h r/wo, ro 14ch?14fh uev uncorrectable error severity 00060011h ro 150h?153h ces correctable error status 00000000h r/wc 154h?157h cem correctable error mask 00000000h r/wo 158h?15bh aecc advanced error ca pabilities and control 00000000h ro 170h?173h res root error status 00000000h r/wc, ro 180h?183h rctcl root complex topology capability list 00010005h ro 184h?187h esd element self description see bit description ro 190h?193h uld upstream link description 00000001h ro 198h?19fh ulba upstream link base address see bit description ro 300-303h pecr2 pci express configuration register 2 60005007h r/w 318h peetm pci express extended test mode register see bit description ro 324h?327h pec1 pci express configuration register 1 00000000h ro, r/w table 20-1. pci express* configuration registers address map (pci express?d28:f0/f1/f2/f3/f4/f5) (sheet 3 of 3) offset mnemonic register name function 0?5 default type http://www..net/ datasheet pdf - http://www..net/ pci express* configuration registers 724 datasheet 20.1.1 vid?vendor identi fication register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 00h ? 01h attribute: ro default value: 8086h size: 16 bits 20.1.2 did?device identi fication register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 02h?03h attribute: ro default value: port 1= bit description size: 16 bits port 2= bit description port 3= bit description port 4= bit description port 5= bit description port 6= bit description bit description 15:0 vendor id ? ro. this is a 16-bit value assigned to intel bit description 15:0 device id ? ro. this is a 16-bit value assigned to the intel ? ich10 pci express controller. refer to the intel ? i/o controller hub (ich10) family for the value of the device id register http://www..net/ datasheet pdf - http://www..net/ datasheet 725 pci express* configuration registers 20.1.3 pcicmd?pci command register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 04h?05h attribute: r/w, ro default value: 0000h size: 16 bits bit description 15:11 reserved 10 interrupt disable ? r/w. this disables pin-based intx# interrupts on enabled hot- plug and power management events. this bit has no e ffect on msi operation. 0 = internal intx# messages are generated if there is an interrupt for hot-plug or power management and msi is not enabled. 1 = internal intx# messages will not be generated. this bit does not affect inte rrupt forwarding from devices connected to the root port. assert_intx and deassert_intx messages wi ll still be forwarded to the internal interrupt controllers if this bit is set. 9 fast back to back enable (fbe) ? reserved per the pci express* base specification . 8 serr# enable (see) ? r/w. 0 = disable. 1 = enables the root port to generate an serr# message when psts.sse is set. 7 wait cycle control (wcc) ? reserved per the pci express base specification . 6 parity error response (per) ? r/w. 0 = disable. 1 = indicates that the device is capable of reporting pa rity errors as a master on the backbone . 5 vga palette snoop (vps) ? reserved per the pci express* base specification . 4 postable memory write enable (pmwe) ? reserved per the pci express* base specification . 3 special cycle enable (sce) ? reserved per the pci express* base specification . 2 bus master enable (bme) ? r/w. 0 = disable. all cycles from the device are master aborted 1 = enable. allows the root port to forw ard cycles onto the backbone from a pci express* device. 1 memory space enable (mse) ? r/w. 0 = disable. memory cycles within the rang e specified by the memory base and limit registers are master aborted on the backbone. 1 = enable. allows memory cycles within th e range specified by the memory base and limit registers can be forwarde d to the pci express device. 0 i/o space enable (iose) ? r/w. this bit controls access to the i/o space registers. 0 = disable. i/o cycles within the range spec ified by the i/o base and limit registers are master aborted on the backbone. 1 = enable. allows i/o cycles within the range specified by the i/o base and limit registers can be forwarded to the pci express device. http://www..net/ datasheet pdf - http://www..net/ pci express* configuration registers 726 datasheet 20.1.4 pcists?pci status register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 06h ? 07h attribute: r/wc, ro default value: 0010h size: 16 bits bit description 15 detected parity error (dpe) ? r/wc. 0 = no parity error detected. 1 = set when the root port receives a command or data from the backbone with a parity error. this is set even if pcimd. per (d28:f0/f1/f2/f3:04, bit 6) is not set. 14 signaled system error (sse) ? r/wc. 0 = no system error signaled. 1 = set when the root port signals a sy stem error to the internal serr# logic. 13 received master abort (rma) ? r/wc. 0 = root port has not received a completion with unsupported re quest status from the backbone. 1 = set when the root port receives a completion with unsupported request status from the backbone. 12 received target abort (rta) ? r/wc. 0 = root port has not received a completion with completer abort from the backbone. 1 = set when the root port receives a completion with completer abort from the backbone. 11 signaled target abort (sta) ? r/wc. 0 = no target abort received. 1 = set whenever the root port forwards a target abort received from the downstream device onto the backbone. 10:9 devsel# timing status (dev_sts) ? reserved per the pci express* base specification . 8 master data parity error detected (dped) ? r/wc. 0 = no data parity error received. 1 = set when the root port receives a comp letion with a data parity error on the backbone and pcimd.per (d28:f0/f 1/f2/f3:04, bit 6) is set. 7 fast back to back capable (fb2bc) ? reserved per the pci express* base specification . 6reserved 5 66 mhz capable ? reserved per the pci express* base specification . 4 capabilities list ? ro. hardwired to 1. indicates th e presence of a capabilities list. 3 interrupt status ? ro. indicates status of ho t-plug and power management interrupts on the root port that re sult in intx# message generation. 0 = interrupt is deasserted. 1 = interrupt is asserted. this bit is not set if msi is enabled. if msi is not enabled, this bit is set regardless of the state of pcicmd.interrupt disable bit (d28:f0/f1/f2/f3/f4/f5:04h:bit 10). 2:0 reserved http://www..net/ datasheet pdf - http://www..net/ datasheet 727 pci express* configuration registers 20.1.5 rid?revision identification register (pci express?d28:f0/f1/f2/f3/f4/f5) offset address: 08h attribute: ro default value: see bit description size: 8 bits 20.1.6 pi?programming interface register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 09h attribute: ro default value: 00h size: 8 bits 20.1.7 scc?sub class code register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 0ah attribute: ro default value: 04h size: 8 bits 20.1.8 bcc?base clas s code register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 0bh attribute: ro default value: 06h size: 8 bits bit description 7:0 revision id ? ro. refer to the intel ? i/o controller hub (ich10) family specification update for the value of the revision id register bit description 7:0 programming interface ? ro. 00h = no specific register level programming interface defined. bit description 7:0 sub class code (scc) ? ro. this field is determined by bit 2 of the mpc register (d28:f0-5:offset d8h, bit 2). 04h = pci-to-pci bridge. 00h = host bridge. bit description 7:0 base class code (bcc) ? ro. 06h = indicates the device is a bridge device. http://www..net/ datasheet pdf - http://www..net/ pci express* configuration registers 728 datasheet 20.1.9 cls?cache line size register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 0ch attribute: r/w default value: 00h size: 8 bits 20.1.10 plt?primary late ncy timer register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 0dh attribute: ro default value: 00h size: 8 bits 20.1.11 headtyp?header type register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 0eh attribute: ro default value: 81h size: 8 bits 20.1.12 bnum?bus nu mber register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 18?1ah attribute: r/w default value: 000000h size: 24 bits bit description 7:0 cache line size (cls) ? r/w. this is read/write but contains no functionality, per the pci express* base specification . bit description 7:3 latency count. reserved per the pci express* base specification. 2:0 reserved bit description 7 multi-function device ? ro. 0 = single-func tion device. 1 = multi-function device. 6:0 configuration layout ? ro. this field is determined by bit 2 of the mpc register (d28:f0-5:offset d8h, bit 2). 00h = indicates a host bridge. 01h = indicates a pci-to-pci bridge . bit description 23:16 subordinate bus number (sbbn) ? r/w. indicates the highest pci bus number below the bridge. 15:8 secondary bus number (scbn) ? r/w. indicates the bus number the port. 7:0 primary bus number (pbn) ? r/w. indicates the bus number of the backbone. http://www..net/ datasheet pdf - http://www..net/ datasheet 729 pci express* configuration registers 20.1.13 slt?secondar y latency timer (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 1bh attribute: ro default value: 00h size: 8 bits 20.1.14 iobl?i/o base and limit register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 1ch?1dh attribute: r/w, ro default value: 0000h size: 16 bits bit description 7:0 secondary latency timer ? reserved for a root port per the pci express* base specification. bit description 15:12 i/o limit address (iola) ? r/w. i/o base bits corresponding to address lines 15:12 for 4-kb alignment. bits 11:0 are assumed to be padded to fffh. 11:8 i/o limit address capability (iolc) ? r/o. indicates that the bridge does not support 32-bit i/o addressing. 7:4 i/o base address (ioba) ? r/w. i/o base bits correspon ding to address lines 15:12 for 4-kb alignment. bits 11:0 are assumed to be padded to 000h. 3:0 i/o base address capability (iobc) ? r/o. indicates that the bridge does not support 32-bit i/o addressing. http://www..net/ datasheet pdf - http://www..net/ pci express* configuration registers 730 datasheet 20.1.15 ssts?secondary status register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 1eh?1fh attribute: r/wc default value: 0000h size: 16 bits bit description 15 detected parity error (dpe) ? r/wc. 0 = no error. 1 = the port received a poisoned tlp . 14 received system error (rse) ? r/wc. 0 = no error. 1 = the port received an err_fatal or err_nonfatal message from the device. 13 received master abort (rma) ? r/wc. 0 = unsupported request not received. 1 = the port received a completion with ?u nsupported request? status from the device. 12 received target abort (rta) ? r/wc. 0 = completion abort not received. 1 = the port received a completion with ?completion abort? status from the device. 11 signaled target abort (sta) ? r/wc. 0 = completion abort not sent. 1 = the port generated a completion with ?completion abort? status to the device. 10:9 secondary devsel# timing status (sdts): reserved per pci express* base specification . 8 data parity error detected (dpd) ? r/wc. 0 = conditions belo w did not occur . 1 = set when the bctrl.pere (d28:fo/f1/f2/f3/f4/f5:3e: bit 0) is set, and either of the following two conditions occurs: ? port receives completi on marked poisoned. ? port poisons a write request to the secondary side. 7 secondary fast back to back capable (sfbc): reserved per pci express* base specification . 6reserved 5 secondary 66 mhz capable (sc66): reserved per pci express* base specification . 4:0 reserved http://www..net/ datasheet pdf - http://www..net/ datasheet 731 pci express* configuration registers 20.1.16 mbl?memory base and limit register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 20h?23h attribute: r/w default value: 00000000h size: 32 bits accesses that are within the ranges specified in this register will be sent to the attached device if cmd.mse (d28:f0/f1/f2/f3/f4/f5:04:bit 1) is set. accesses from the attached device that are outside the ranges specified will be forwarded to the backbone if cmd.bme (d28:f0/f1/f2/f3/f4/f5:04:bit 2) is set. the comparison performed is mb ad[31:20] ml. 20.1.17 pmbl?prefetchable memory base and limit register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 24h?27h attribute: r/w, ro default value: 00010001h size: 32 bits accesses that are within the ranges specified in this register will be sent to the device if cmd.mse (d28:f0/f1/f2/f3/f4/f5;04, bit 1) is set. accesses from the device that are outside the ranges specified will be forwarded to the backbone if cmd.bme (d28:f0/f1/ f2/f3/f4/f5;04, bit 2) is set. the comparison performed is pmbu32:pmb ad[63:32]:ad[31:20] pmlu32:pml. 20.1.18 pmbu32?prefetchable me mory base upper 32 bits register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 28h?2bh attribute: r/w default value: 00000000h size: 32 bits bit description 31:20 memory limit (ml) ? r/w. these bits are compared with bits 31:20 of the incoming address to determine the upper 1- mb aligned value of the range. 19:16 reserved 15:4 memory base (mb) ? r/w. these bits are compared with bits 31:20 of the incoming address to determine the lower 1- mb aligned value of the range. 3:0 reserved bit description 31:20 prefetchable memory limit (pml) ? r/w. these bits are compared with bits 31:20 of the incoming address to determine th e upper 1-mb aligned value of the range. 19:16 64-bit indicator (i64l) ? ro. indicates suppor t for 64-bit addressing 15:4 prefetchable memory base (pmb) ? r/w. these bits are compared with bits 31:20 of the incoming address to determine th e lower 1-mb aligned value of the range. 3:0 64-bit indicator (i64b) ? ro. indicates support for 64-bit addressing bit description 31:0 prefetchable memory base upper portion (pmbu) ? r/w. upper 32-bits of the prefetchable address base. http://www..net/ datasheet pdf - http://www..net/ pci express* configuration registers 732 datasheet 20.1.19 pmlu32?prefetchable memory limit upper 32 bits register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 2ch?2fh attribute: r/w default value: 00000000h size: 32 bits 20.1.20 capp?capabilities list pointer register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 34h attribute: r0 default value: 40h size: 8 bits 20.1.21 intr?interrupt information register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 3ch?3dh attribute: r/w, ro default value: see bit description size: 16 bits function level reset: no (bits 7:0 only) bit description 31:0 prefetchable memory limit upper portion (pmlu) ? r/w. upper 32-bits of the prefetchable address limit. bit description 7:0 capabilities pointer (ptr) ? ro. indicates that the pointe r for the first entry in the capabilities list is at 40h in configuration space. bit description 15:8 interrupt pin (ipin) ? ro. indicates the interrupt pin driven by the root port. at reset, this register takes on the following values, which re flect the reset state of the d28ip register in chipset config space: note: the value that is programmed into d28ip is always reflected in this register. 7:0 interrupt line (iline) ? r/w. default = 00h. software written value to indicate which interrupt line (vector) the interrupt is connected to. no hardware action is taken on this register. these bi ts are not reset by flr. port reset value 1d28ip.p1ip 2d28ip.p2ip 3d28ip.p3ip 4d28ip.p4ip 5d28ip.p5ip http://www..net/ datasheet pdf - http://www..net/ datasheet 733 pci express* configuration registers 20.1.22 bctrl?bridge control register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 3eh?3fh attribute: r/w default value: 0000h size: 16 bits bit description 15:12 reserved 11 discard timer serr# enable (dtse): reserved per pci express* base specification, revision 1.0a 10 discard timer status (dts): reserved per pci express* base specification, revision 1.0a. 9 secondary discard timer (sdt): reserved per pci express* base specification, revision 1.0a. 8 primary discard timer (pdt): reserved per pci express* base specification, revision 1.0a. 7 fast back to back enable (fbe): reserved per pci express* base specification, revision 1.0a. 6 secondary bus reset (sbr) ? r/w. triggers a hot rese t on the pci express* port. 5 master abort mode (mam): reserved per express specification. 4 vga 16-bit decode (v16) ? r/w. 0 = vga range is enabled. 1 = the i/o aliases of the vga range (see bc trl:ve definition belo w), are not enabled, and only the base i/o ranges can be decoded 3 vga enable (ve) ? r/w. 0 = the ranges below will not be claimed off the backbone by the root port. 1 = the following ranges will be claime d off the backbone by the root port: ? memory ranges a0000h-bffffh ? i/o ranges 3b0h ? 3bbh and 3c0h ? 3dfh, and a ll aliases of bits 15:10 in any combination of 1s 2 isa enable (ie) ? r/w. this bit only applies to i/ o addresses that are enabled by the i/o base and i/o limit registers and are in the first 64 kb of pci i/o space. 0 = the root port will not block any forwar ding from the backbone as described below. 1 = the root port will block any forwarding from the backbone to the device of i/o transactions addressing the last 768 by tes in each 1-kb block (offsets 100h to 3ffh). 1 serr# enable (se) ? r/w. 0 = the messages descri bed below are not forwarded to the backbone. 1 = err_cor, err_nonfatal, and err_fatal messages received are forwarded to the backbone. 0 parity error respon se enable (pere) ? r/w. 0 = poisoned write tlps and completions indicating poisoned tlps will not set the ssts.dpd (d28:f0/f1/f2/f3/f4/f5:1e, bit 8). 1 = poisoned write tlps and completions indicating poisoned tlps will set the ssts.dpd (d28:f0/f1/f2/f3/f4/f5:1e, bit 8). http://www..net/ datasheet pdf - http://www..net/ pci express* configuration registers 734 datasheet 20.1.23 clist?capabilities list register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 40?41h attribute: ro default value: 8010h size: 16 bits 20.1.24 xcap?pci express* capabilities register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 42h?43h attribute: r/wo, ro default value: 0041h size: 16 bits bit description 15:8 next capability (next) ? ro. value of 80h indicates the location of the next pointer. 7:0 capability id (cid) ? ro. indicates this is a pci express* capability. bit description 15:14 reserved 13:9 interrupt message number (imn) ? ro. the intel ? ich10 does not have multiple msi interrupt numbers. 8 slot implemented (si) ? r/wo. indicates whether the ro ot port is connected to a slot. slot support is platform specific. bios programs this field, and it is maintained until a platform reset. 7:4 device / port type (dt) ? ro. indicates this is a pci express* root port. 3:0 capability version (cv) ? ro. indicates pci express 1.0. http://www..net/ datasheet pdf - http://www..net/ datasheet 735 pci express* configuration registers 20.1.25 dcap?device capa bilities register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 44h?47h attribute: ro default value: 00008fc0h size: 32 bits bit description 31:28 reserved 27:26 captured slot power limit sc ale (csps) ? ro. not supported. 25:18 captured slot power limit va lue (cspv) ? ro. not supported. 17:16 reserved 15 role based error reporting (rber) ? ro. indicates that this device implements the functionality defined in th e error reporting ecn as required by the pci express 1.1 spec. 14:12 reserved 11:9 endpoint l1 acceptable latency (e1al) ? ro. this field is reserved with a setting of 000b for devices other than endpoin ts, per the pci express 1.1 spec. 8:6 endpoint l0s acceptable latency (e0al) ? ro. this field is reserved with a setting of 000b for devices other than endpoin ts, per the pci express 1.1 spec. 5 extended tag field supported (etfs) ? ro. indicates that 8-bit tag fields are supported. 4:3 phantom functions supported (pfs) ? ro. no phantom functions supported. 2:0 max payload size supported (mps) ? ro. indicates the maximum payload size supported is 128b. http://www..net/ datasheet pdf - http://www..net/ pci express* configuration registers 736 datasheet 20.1.26 dctl?device control register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 48h?49h attribute: r/w, ro default value: 0000h size: 16 bits bit description 15 reserved 14:12 max read request size (mrrs) ? ro. hardwired to 0. 11 enable no snoop (ens) ? ro. not supported. the root port will never issue non-snoop requests. 10 aux power pm enable (apme) ? r/w. the os will set th is bit to 1 if the device connected has detected aux power. it has no effect on the root port otherwise. 9 phantom functions enable (pfe) ? ro. not supported. 8 extended tag field enable (etfe) ? ro. not supported. 7:5 max payload size (mps) ? r/w. the root port only supports 128-b payloads, regardless of the programming of this field. 4 enable relaxed ordering (ero) ? ro. not supported. 3 unsupported request reporting enable (ure) ? r/w. 0 = the root port will ignore unsupported request errors. 1 = allows signaling err_nonfatal, err_fa tal, or err_cor to the root control register when detecting an unmasked un supported request (ur). an err_cor is signaled when a unmasked advisory non- fatal ur is received. an err_fatal, err_or nonfatal, is sent to the root control register when an uncorrectable non- advisory ur is received wi th the severity set by the uncorrectable error severity register. 2 fatal error reporting enable (fee) ? r/w. 0 = the root port will ignore fatal errors. 1 = enables signaling of err_fatal to the root control register due to internally detected errors or error mess ages received across the li nk. other bits also control the full scope of related error reporting. 1 non-fatal error reporting enable (nfe) ? r/w. 0 = the root port will ignore non-fatal errors. 1 = enables signaling of err_nonfatal to th e root control register due to internally detected errors or error mess ages received across the li nk. other bits also control the full scope of related error reporting. 0 correctable error reporting enable (cee) ? r/w. 0 = the root port will ignore correctable errors. 1 = enables signaling of err_corr to the root control register due to internally detected errors or error mess ages received across the li nk. other bits also control the full scope of related error reporting. http://www..net/ datasheet pdf - http://www..net/ datasheet 737 pci express* configuration registers 20.1.27 dsts?device status register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 4ah?4bh attribute: r/wc, ro default value: 0010h size: 16 bits bit description 15:6 reserved 5 transactions pending (tdp) ? ro. this bit has no mean ing for the root port since only one transaction may be pending to the intel ? ich10, so a read of this bit cannot occur until it has already returned to 0. 4 aux power detected (apd) ? ro. the root port contains aux power for wakeup. 3 unsupported request detected (urd) ? r/wc. indicates an unsupported request was detected. 2 fatal error detected (fed) ? r/wc. indicates a fatal error was detected. 0 = fatal has not occurred. 1 = a fatal error occurred from a data link prot ocol error, link training error, buffer overflow, or malformed tlp. 1 non-fatal error detected (nfed) ? r/wc. indicates a non- fatal error was detected. 0 = non-fatal has not occurred. 1 = a non-fatal error occurred from a po isoned tlp, unexpected completions, unsupported requ ests, completer abort, or completer timeout. 0 correctable error detected (ced) ? r/wc. indicates a correctable error was detected. 0 = correctable has not occurred. 1 = the port received an internal correct able error from receiver errors / framing errors, tlp crc error, dllp crc error, replay num rollover, replay timeout. http://www..net/ datasheet pdf - http://www..net/ pci express* configuration registers 738 datasheet 20.1.28 lcap?link capa bilities register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 4ch ? 4fh attribute: r/wo, ro default value: see bit description size: 32 bits bit description 31:24 port number (pn) ? ro. indicates the port number for the root port. this value is different for each implemented port: 23:22 reserved 21 (corporate only) link bandwidth notification capability (lbnc) ? ro. 0 = indicates root port can on ly support x1 link widths. 1 = indicates root port can support link widths greater than x1. note: ports 1, 3, and 5 are required to set th is bit. ports 2, 4 and 6 can optionally set this bit. 21 (consumer only) reserved 20 link active reporting capable (larc) ? ro. hardwired to 1 to indicate that this port supports the optional capability of reporting the dl_active state of the data link control and management state machine. 19:18 reserved 17:15 l1 exit latency (el1) ? ro. set to 010b to indicate an exit latency of 2 s to 4 s. 14:12 l0s exit latency (el0) ? ro. indicates as exit latency based upon common- clock configuration. note: lclt.ccc is at d28:f0/f 1/f2/f3/f4/f5:50h:bit 6 function port # value of pn field d28:f0 1 01h d28:f1 2 02h d28:f2 3 03h d28:f3 4 04h d28:f4 5 05h d28:f5 6 06h lclt.ccc value of el0 (these bits) 0 mpc.ucel (d28:f0/f1/f2/f3:d8h:bits20:18) 1 mpc.ccel (d28:f0/f1/f2/f3:d8h:bits17:15) http://www..net/ datasheet pdf - http://www..net/ datasheet 739 pci express* configuration registers 11:10 active state link pm support (apms) ? r/wo. indicates what level of active state link power management is supported on the root port. 9:4 maximum link width (mlw) ? ro. for the root ports, several values can be taken, based upon the value of the chipse t config register fi eld rpc.pc1 (chipset config registers:offset 0224h:bits1:0) fo r ports 1-4 and rpc.pc2 (chipset config registers:offset 0224h:bi ts1:0) for ports 5 and 6 3:0 maximum link speed (mls) ? ro. set to 1h to indicate the link speed is 2.5 gb/s. bit description bits definition 00b neither l0s nor l1 are supported 01b l0s entry supported 10b l1 entry supported 11b both l0s and l1 entry supported value of mlw field port # rpc.pc1=00b rpc.pc1=11b 1 01h 04h 2 01h 01h 3 01h 01h 4 01h 01h port # rpc.pc2=00b rpc.pc2=11b 5 01h n/a http://www..net/ datasheet pdf - http://www..net/ pci express* configuration registers 740 datasheet 20.1.29 lctl?link co ntrol register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 50h-51h attribute: r/w, ro default value: 0000h size: 16 bits bit description 15:8 reserved 7 extended synch (es) ? r/w. 0 = extended sy nch disabled. 1 = forces extended transmission of fts ordered sets in fts and extra ts2 at exit from l1 prior to entering l0. 6 common clock conf iguration (ccc) ? r/w. 0 = the ich10 and device are not using a common reference clock. 1 = the ich10 and device are operating wi th a distributed co mmon reference clock. 5 retrain link (rl) ? r/w. 0 = this bit always returns 0 when read. 1 = the root port will tr ain its downstream link. note: software uses lsts.lt (d28:f0/f1/f2/f3/f4/f5:52, bit 11) to check the status of training. note: it is permitted to write 1b to this bi t while simultaneously writing modified values to other fields in this register. if the ltssm is not already in recovery or configuration, the resulting link training must use the modified values. if the ltssm is already in recovery or configuration, the modified values are not required to affect the link traini ng that is already in progress. 4 link disable (ld) ? r/w. 0 = link enabled. 1 = the root port will disable the link. 3 read completion bo undary control (rcbc) ? ro. indicates the read completion boundary is 64 bytes. 2reserved 1:0 active state link pm control (apmc) ? r/w. indicates whether the root port should enter l0s or l1 or both. 00 = disabled 01 = l0s entry enabled 10 = l1 entry enabled 11 = l0s and l1 entry enabled http://www..net/ datasheet pdf - http://www..net/ datasheet 741 pci express* configuration registers 20.1.30 lsts?link status register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 52h?53h attribute: ro default value: see bit description size: 16 bits bit description 15:14 reserved 13 data link layer active (dlla) ? ro. default value is 0b. 0 = data link control and management state machine is not in the dl_active state 1 = data link control and management st ate machine is in the dl_active state 12 slot clock configuration (scc) ? ro. set to 1b to indicate that the intel ? ich10 uses the same reference clock as on the platform and does not generate its own clock. 11 link training (lt) ? ro. default value is 0b. 0 = link training completed. 1 = link training is occurring. 10 link training error (lte ) ? ro. not supported. set value is 0b. 9:4 negotiated link width (nlw) ? ro. this field indicates the negotiated width of the given pci express* link. the contents of this nlw field is undefined if the link has not successfully trained. note: 000001b = x1 link width, 000010b =x2 linkwidth, 000100b = x4 linkwidth 3:0 link speed (ls) ? ro. this field indica tes the negotiated link speed of the given pci express* link. 01h = link is 2.5 gb/s. port # possible values 1 000001b, 000010b, 000100b 2 000001b 3 000001b 4 000001b 5 000001b, 000010b 6 000001b http://www..net/ datasheet pdf - http://www..net/ pci express* configuration registers 742 datasheet 20.1.31 slcap?slot capa bilities register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 54h ? 57h attribute: r/wo, ro default value: 00000060h (consumer only) size: 32 bits 00040060h (corporate only) bit description 31:19 physical slot number (psn) ? r/wo. this is a value that is unique to the slot number. bios sets this field and it remains set until a platform reset. 18:17 reserved. corporate only 10h. consumer only 00h 16:15 slot power limit scale (sls) ? r/wo. specifies the scale used for the slot power limit value. bios sets this field and it remains set unti l a platform reset. 14:7 slot power limit value (slv) ? r/wo. specifies the upper limit (in conjunction with sls value), on the upper limi t on power supplied by the sl ot. the two values together indicate the amount of power in watts allowed for the slot. bios sets this field and it remains set until a platform reset. 6 hot plug capable (hpc) ? r/wo. 1b = indicates that ho t-plug is supported. 5 hot plug surprise (hps) ? r/wo. 1b = indicates the device may be removed from the slot without prior notification. 4 power indicator present (pip) ? ro. 0b = indicates that a power indicato r led is not present for this slot. 3 attention indicator present (aip) ? ro. 0b = indicates that an attention indica tor led is not present for this slot. 2 mrl sensor present (msp) ? ro. 0b = indicates that an mrl sensor is not present. 1 power controller present (pcp) ? ro. 0b = indicates that a po wer controller is not im plemented for this slot. 0 attention button present (abp) ? ro. 0b = indicates that an attention butt on is not implemen ted for this slot. http://www..net/ datasheet pdf - http://www..net/ datasheet 743 pci express* configuration registers 20.1.32 slctl?slot control register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 58h ? 59h attribute: r/w, ro default value: 0000h size: 16 bits bit description 15:13 reserved 12 link active changed enable (lace) ? r/w. when set, this field enables generation of a hot plug interrupt when the data link layer link active field (d28:f0/f1/f2/f3/f4/f5:52h:bit 13) is changed. 11 reserved 10 power controller control (pcc) ? ro.this bit has no meaning for module based hot-plug. 9:6 (corporate only) reserved 9:8 (consumer only) power indicator control (pic) ? r/w. when read, the current state of the power indicator is returned. when writ ten, the appropriate power_indicator_* messages are sent. defined encodings are: 7:6 (consumer only) attention indicator control (aic) ? r/w. when read, th e current state of the attention indicator is returned. when written, the appropriate attention_indicator_* messages are sent. defined encodings are: 5 hot plug interrupt enable (hpe) ? r/w. 0 = hot plug interrupts based on hot-plug events is disabled. 1 = enables generation of a hot-plug interrupt on enabled hot-plug events. 4 (consumer only) command completed interrupt enable (cce) ? r/w. 0 = hot plug interrupts based on command completions is disabled. 1 = enables the generation of a hot-plug interrupt when a command is completed by the hot-plug controller. 4 (corporate only) reserved 3 presence detect changed enable (pde) ? r/w. 0 = hot plug interrupts based on presen ce detect logic changes is disabled. 1 = enables the generation of a hot-plug interrupt or wake message when the presence detect lo gic changes state. bits definition 00b reserved 01b on 10b blink 11b off bits definition 00b reserved 01b on 10b blink 11b off http://www..net/ datasheet pdf - http://www..net/ pci express* configuration registers 744 datasheet 20.1.33 slsts?slot status register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 5ah ? 5bh attribute: r/wc, ro default value: 0000h size: 16 bits 2:1 reserved. 0 attention button pressed enable (abe) ? r/w. when set, enables the generation of a hot-plug interrupt wh en the attention button is pressed. 0 = hot plug interrupts based on the atte ntion button being pressed is disabled. 1 = enables the generation of a hot-plug interrupt when the attention button is pressed. bit description bit description 15:9 reserved 8 link active state changed (lasc) ? r/wc. 1 = this bit is set when the value reported in data link layer link active field of the link status register (d28:f0/f1/f2/f3/f4/f5:52h:bit 13) is changed. in response to a data link layer state ch anged event, software must read data link layer link active field of the link st atus register to dete rmine if the link is active before initiating configuratio n cycles to the ho t plugged device. 7reserved 6 presence detect state (pds) ? ro. if xcap.si (d28:f0/f1/f2/f3/f4/f5:42h:bit 8) is set (indicating that this root port spawns a slot), then this bit: 0 = indicates the slot is empty. 1 = indicates the slot has a device connected. otherwise, if xcap.si is cleare d, this bit is always set (1). 5 mrl sensor state (ms) ? reserved as the mrl sensor is not implemented. 4 (corporate only) reserved 4 (consumer only) command completed (cc) ? r/wc. 0 = issued comman d not completed. 1 = the hot-plug controller completed an issued command. this is set when the last message of a command is sent and indicates that software can write a new command to the slot controller. 3 presence detect changed (pdc) ? r/wc. 0 = no change in the pds bit. 1 = the pds bit changed states. 2 mrl sensor changed (msc) ? reserved as the mrl sensor is not implemented. 1 power fault detected (pfd) ? reserved as a power controller is not implemented. 0 (corporate only) reserved 0 (consumer only) attention button pressed (abp) ? r/wc. 0 = the attention button has not been pressed. 1 = the attention bu tton is pressed. http://www..net/ datasheet pdf - http://www..net/ datasheet 745 pci express* configuration registers 20.1.34 rctl?root control register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 5ch ? 5dh attribute: r/w default value: 0000h size: 16 bits 20.1.35 rsts?root status register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 60h ? 63h attribute: r/wc, ro default value: 00000000h size: 32 bits bit description 15:4 reserved 3 pme interrupt enable (pie) ? r/w. 0 = interrupt generation disabled. 1 = interrupt generation enabled when pc ists.inerrupt status (d28:f0/f1/f2/f3/f4/ f5:60h, bit 16) is in a set state (either due to a 0 to 1 transition, or due to this bit being set with rsts.is already set). 2 system error on fatal error enable (sfe) ? r/w. 0 = an serr# will not be generated. 1 = an serr# will be generated, assumi ng cmd.see (d28:f0/f1/f2/f3/f4/f5:04, bit 8) is set, if a fatal erro r is reported by any of the de vices in the hierarchy of this root port, including fatal e rrors in this root port. 1 system error on non-fatal error enable (sne) ? r/w. 0 = an serr# will not be generated. 1 = an serr# will be generated, assumi ng cmd.see (d28:f0/f1/f2/f3/f4/f5:04, bit 8) is set, if a non-fatal error is reported by any of th e devices in the hierarchy of this root port, including non-fatal errors in this root port. 0 system error on correctable error enable (sce) ? r/w. 0 = an serr# will not be generated. 1 = an serr# will be generated, assumi ng cmd.see (d28:f0/f1/f2/f3/f4/f5:04, bit 8) if a correctable error is reported by any of the devices in the hierarchy of this root port, including correctable errors in this root port. bit description 31:18 reserved 17 pme pending (pp) ? ro. 0 = when the original pme is cleared by softwa re, it will be set again, the requestor id will be updated, and th is bit will be cleared. 1 = indicates another pme is pendin g when the pme status bit is set. 16 pme status (ps) ? r/wc. 0 = pme was not asserted. 1 = indicates that pme was asserted by the requestor id in rid. subsequent pmes are kept pending until th is bit is cleared. 15:0 pme requestor id (rid) ? ro. indicates the pci requ estor id of the last pme requestor. valid only when ps is set. http://www..net/ datasheet pdf - http://www..net/ pci express* configuration registers 746 datasheet 20.1.36 dcap2?device capabilities 2 register (corporate only) (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 64h ? 67h attribute: ro default value: 00000016h size: 32 bits 20.1.37 dctl2?device control 2 register (corporate only) (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 68h ? 69h attribute: ro, r/w default value: 0000h size: 16 bits bit description 31:5 reserved 4 completion timeout disa ble supported (ctds) ? ro. a value of 1b indicates support for the comple tion timeout disable mechanism. 3:0 completion timeout ranges supported (ctrs) ? ro. this field indicates device support for the optional completion ti meout programmability mechanism. this mechanism allows system software to modify the completion timeout value. this field is hardwired to support 10 ms to 250 ms and 250 ms to 4 s. bit description 15:5 reserved 4 completion timeout disable (ctd) ? rw. when set to 1b, this bit disables the completion timeout mechanism. if there are outstanding requests when the bit is cleared, it is permitted but not required for hardware to apply the comple tion timeout mechanism to the outstanding requests. if this is done, it is permitted to base the start ti me for each request on either the time this bit was cleared or the time each request was issued. 3:0 completion timeout value (ctv) ? rw. this field allows system software to modify the completion timeout value. 0000b = 40?50 ms (default) (specification range 50 us to 50 ms) 0101b = 40?50 ms (specification range is 16 ms to 55 ms) 0110b = 160?170 ms (specification range is 65 ms to 210 ms) 1001b = 400?500 ms (specification range is 260 ms to 900 ms) 1010b = 1.6?1.7 s (specification range is 1 s to 3.5 s) all other values are reserved. note: software is permitted to ch ange the value in this field at any time. for requests already pending when the completion ti meout value is changed, hardware is permitted to use either the new or the old value for the outstanding requests, and is permitted to base th e start time for each requ est either on when this value was changed or on when each request w as issued. http://www..net/ datasheet pdf - http://www..net/ datasheet 747 pci express* configuration registers 20.1.38 lctl2?link control 2 register (corporate only) (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 70h ? 71h attribute: ro default value: 0001h size: 16 bits 20.1.39 mid?message signaled in terrupt identifi ers register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 80h?81h attribute: ro default value: 9005h size: 16 bits 20.1.40 mc?message signaled inte rrupt message control register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 82?83h attribute: r/w, ro default value: 0000h size: 16 bits bit description 15:4 reserved 3:0 target link speed (tls) ? ro. this field sets an upper limit on link operational speed by restricting the values advertised by the upstream component in its training sequences. 0001b = 2.5 gt/s target link speed all other values reserved bit description 15:8 next pointer (next) ? ro. indicates the location of the next pointer in the list. 7:0 capability id (cid) ? ro. capabilities id indicates msi. bit description 15:8 reserved 7 64 bit address capable (c64) ? ro. capable of generating a 32-bit message only. 6:4 multiple message enable (mme) ? r/w. these bits are r/w for software compatibility, but only one message is ever sent by the root port. 3:1 multiple message capable (mmc) ? ro. only one message is required. 0 msi enable (msie) ? r/w. 0 = msi is disabled. 1 = msi is enabled and traditional interrupt pins are not used to generate interrupts. note: cmd.bme (d28:f0/f1/f2/f3/f4/f5:04h:bit 2) must be set for an msi to be generated. if cmd.bme is clea red, and this bit is set, no interrupts (not even pin based) are generated. http://www..net/ datasheet pdf - http://www..net/ pci express* configuration registers 748 datasheet 20.1.41 ma?message signaled interrupt message address register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 84h ? 87h attribute: r/w default value: 00000000h size: 32 bits 20.1.42 md?message signaled in terrupt message data register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 88h ? 89h attribute: r/w default value: 0000h size: 16 bits 20.1.43 svcap?subsystem vend or capability register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 90h ? 91h attribute: ro default value: a00dh size: 16 bits 20.1.44 svid?subsystem vendor identification register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 94h ? 97h attribute: r/wo default value: 00000000h size: 32 bits bit description 31:2 address (addr) ? r/w. lower 32 bits of the system specified message address, always dw aligned. 1:0 reserved bit description 15:0 data (data) ? r/w. this 16-bit field is programmed by system software if msi is enabled. its content is driven onto the lo wer word (pci ad[15:0]) during the data phase of the msi memory write transaction. bit description 15:8 next capability (next) ? ro. indicates the location of the next pointer in the list. 7:0 capability identifier (cid) ? ro. value of 0dh indicates this is a pci bridge subsystem vendor capability. bit description 31:16 subsystem identifier (sid) ? r/wo. indicates the subsys tem as identified by the vendor. this field is write once and is locked down until a bridge reset occurs (not the pci bus reset). 15:0 subsystem vendor identifier (svid) ? r/wo. indicates the manufacturer of the subsystem. this field is write once and is locked down until a bridge rese t occurs (not the pci bus reset). http://www..net/ datasheet pdf - http://www..net/ datasheet 749 pci express* configuration registers 20.1.45 pmcap?power manageme nt capability register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: a0h ? a1h attribute: ro default value: 0001h size: 16 bits 20.1.46 pmc?pci power manageme nt capabilities register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: a2h ? a3h attribute: ro default value: c802h size: 16 bits bit description 15:8 next capability (next) ? ro. indicates this is th e last item in the list. 7:0 capability identifier (cid) ? ro. value of 01h indicates this is a pci power management capability. bit description 15:11 pme_support (pmes) ? ro. indicates pme# is supported for states d0, d3 hot and d3 cold . the root port does not generate pme#, but reporting that it does is necessary for some legacy operating systems to enable pme# in devices connected behind this root port. 10 d2_support (d2s) ? ro. the d2 state is not supported. 9 d1_support (d1s) ? ro the d1 state is not supported. 8:6 aux_current (ac) ? ro. reports 375 ma maximum suspend well current required when in the d3 cold state. 5 device specific initialization (dsi) ? ro. 1 = indicates that no device-specific initialization is required. 4 reserved 3 pme clock (pmec) ? ro. 1 = indicates that pci clock is not required to generate pme#. 2:0 version (vs) ? ro. indicates support for revision 1.1 of the pci power management specification . http://www..net/ datasheet pdf - http://www..net/ pci express* configuration registers 750 datasheet 20.1.47 pmcs?pci power mana gement control and status register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: a4h ? a7h attribute: r/w, ro default value: 00000000h size: 32 bits bit description 31:24 reserved 23 bus power / clock control enable (bpce) ? reserved per pci express* base specification, revision 1.0a . 22 b2/b3 support (b23s) ? reserved per pci express* base specification, revision 1.0a . 21:16 reserved 15 pme status (pmes) ? ro. 1 = indicates a pme was receiv ed on the downstream link. 14:9 reserved 8 pme enable (pmee) ? r/w. 1 = indicates pme is enabled. th e root port takes no action on this bit, but it must be r/w for some legacy operating systems to enable pme# on devices connected to this root port. this bit is sticky and resides in the resume well. the reset for this bit is rsmrst# which is not asserted du ring a warm reset. 7:2 reserved 1:0 power state (ps) ? r/w. this field is used both to determine the current power state of the root port and to set a new power state. the values are: 00 = d0 state 11 = d3 hot state note: when in the d3 hot state, the controller?s config uration space is available, but the i/o and memory spaces are not. type 1 configuration cycles are also not accepted. interrupts are not required to be blocked as software will disable interrupts prior to placing the port into d3 hot . if software attempts to write a ?10? or ?01? to these bits, the write will be ignored. http://www..net/ datasheet pdf - http://www..net/ datasheet 751 pci express* configuration registers 20.1.48 mpc2?miscellan eous port configura tion register 2 (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: d4h ? d7h attribute: r/w, ro default value: 00000000h size: 32 bits bit description 31:5 reserved. 4 (corporate only) aspm control override enable (aspmcoen) ? rw. 1 = dmi will use the values in th e aspm control override registers 0 = dmi will use the aspm registers in the link control register. notes: this register allows bios to contro l the dmi aspm settings instead of the os. 4 (consumer only) reserved 3:2 (corporate only) aspm control override (aspmo) ? rw. provides bios control of whether dmi should enter l0s or l1 or both. 00 = disabled 01 = l0s entry enabled 10 = l1 entry enabled 11 = l0s and l1 entry enabled. 3:2 (consumer only) reserved 1 eoi forwarding disable (eoifd) ? r/w. when set, eoi messages are not claimed on the backbone by this port an wi ll not be forwarded ac ross the pcie link. 0 = eoi forwarding is disabled. 1 = eoi forwarding is enabled. 0 l1 completion timeout mode (lictm) ? r/w. 0 = pci express specification compliant. completion timeout is disabled during software initiated l1, and enab led during aspm initiate l1. 1 = completion timeout is en abled during l1, regardless of how l1 entry was initiated. http://www..net/ datasheet pdf - http://www..net/ pci express* configuration registers 752 datasheet 20.1.49 mpc?miscellaneous port configuration register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: d8h ? dbh attribute: r/w, ro default value: 08110000h size: 32 bits bit description 31 power management sci enable (pmce) ? r/w. 0 = sci generation based on a powe r management event is disabled. 1 = enables the root port to generate sci whenever a power management event is detected. 30 hot plug sci enable (hpce) ? r/w. 0 = sci generation based on a hot-plug event is disabled. 1 = enables the root port to generate sci whenever a hot-plug event is detected. 29 link hold off (lho) ? r/w. 1 = port will not take any tlp. this is us ed during loopback mode to fill up the downstream queue. 28 address translator enable (ate) ? r/w. this bit is used to enable address translation via the at bits in this register during loopback mode. 0 = disable 1 = enable 27 lane reversal (lr) ? r/o. consumer only: this regi ster reads the setting of the sataled# strap. corporate only: this register reads th e setting of the pcielr1 soft strap. 0 = pci express lanes 0-3 are reversed. 1 = no lane reversal (default). note: the port configuration straps must be set such that port 1 is configured as a x4 port using lanes 0-3 when lane reversal is enabled. x2 lane reversal is not supported. note: this register is on ly valid on port 1. 26 invalid receive bus number check enable (irbnce) ? r/w. when set, the receive transaction layer will signal an e rror if the bus number of a memory request does not fall within the range between scbn and sbbn. if this check is enabled and the request is a memory write, it is treated as an unsupported reques t. if this check is enabled and the request is a non-posted memory read reques t, the request is considered a malformed tlp and a fatal error. messages, i/o, config, an d completions are never ch ecked for valid bus number. 25 invalid receive range check enable (irrce) ? r/w. when set, the receive transaction layer will treat the tlp as an unsupported request error if the address range of a memory request does not outside the range between prefetchable and non- prefetchable ba se and limit. messages, i/o, configuration, and comple tions are never checked for valid address ranges. 24 bme receive check enable (bmerce) ? r/w. when set, the receive transaction layer will treat the tlp as an unsupported request error if a me mory read or write request is received and the bus master enable bit is not set. messages, io, config, and comple tions are never checked for bme. 23 reserved http://www..net/ datasheet pdf - http://www..net/ datasheet 753 pci express* configuration registers 22 detect override (forcedet) ? r/w. 0 = normal operation. detected output fro m afe is sampled for presence detection. 1 = override mode. ignores afe de tect output and link training proceeds as if a device were detected. 21 flow control during l1 entry (fcdl1e) ? r/w. 0 = no flow control update dllps se nt during l1 ack transmission. 1 = flow control update dllps sent during l1 ack transmission as required to meet the 30 s periodic flow control update. 20:18 unique clock exit latency (ucel) ? r/w. this value represents the l0s exit latency for unique-clock configurations (lctl.ccc = 0) (d 28:f0/f1/f2/f3/f4/ f5:offset 50h:bit 6). it defaults to 512 ns to less than 1 s, bu t may be overridden by bios. 17:15 common clock exit latency (ccel) ? r/w. this value represents the l0s exit latency for common-clock configurations (lctl.ccc = 1) (d28:f0/f 1/f2/f3/f4/ f5:offset 50h:bit 6). it defaults to 128 ns to less than 256 ns, but may be overridden by bios. 14:8 reserved 7 port i/oxapic enable (pae) ? r/w. 0 = hole is disabled. 1 = a range is opened through the bri dge for the followin g memory addresses: 6:3 reserved 2 bridge type (bt) ? ro. this register can be used to modify the base class and header type fields from the default p2p bridge to a host bridge. having the root port appear as a host bridge is useful in some server configurations. 0 = the root port bridge type is a p2p br idge, header sub-class = 04h, and header type = type 1 . 1 = the root port bridge type is a p2p br idge, header sub-class = 00h, and header type = type 0 . 1 hot plug smi enable (hpme) ? r/w. 0 = smi generation based on a hot-plug event is disabled. 1 = enables the root port to generate smi whenever a hot-plug event is detected. 0 power management sm i enable (pmme) ? r/w. 0 = smi generation based on a powe r management event is disabled. 1 = enables the root port to generate sm i whenever a power management event is detected. bit description port # address 1 fec1_0000h ? fec1_7fffh 2 fec1_8000h ? fec1_ffffh 3 fec2_0000h ? fec2_7fffh 4 fec2_8000h ? fec2_ffffh 5 fec3_0000h ? fec3_7fffh 6 fec3_8000h ? fec3_ffffh http://www..net/ datasheet pdf - http://www..net/ pci express* configuration registers 754 datasheet 20.1.50 smscs?smi/sci status register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: dch ? dfh attribute: r/wc default value: 00000000h size: 32 bits bit description 31 power management sci status (pmcs) ? r/wc. 1 = pme control logic needs to generate an interrupt, and this interrupt has been routed to generate an sci. 30 hot plug sci status (hpcs) ? r/wc. 1 = hot-plug controller needs to generate an interrupt, and has this interrupt been routed to generate an sci. 29:5 reserved 4 hot plug link active state changed smi status (hplas) ? r/wc. 1 = slsts.lasc (d28:f0/f1/f2/f3/f4/f5:5a, bit 8) transitioned from 0-to-1, and mpc.hpme (d28:f0/f1/f2/f3/f4/f5:d8, bit 1) is set. when this bit is set, an smi# will be generated. 3 hot plug command comple ted smi status (hpccm) ? r/wc. 1 = slsts.cc (d28:f0/f1/f2/f3/f4/f5:5a, bit 4) transitioned from 0-to-1, and mpc.hpme (d28:f0/f1/f2/f3/f4/f5:d8, bit 1) is set. when this bit is set, an smi# will be generated. 2 hot plug attention button smi status (hpabm) ? r/wc. 1 = slsts.abp (d28:f0/f1/f2/f3/f4/f5:5a, bit 0) transitioned from 0-to-1, and mpc.hpme (d28:f0/f1/f2/f3/f4/f5:d8, bit 1) is set. when this bit is set, an smi# will be generated. 1 hot plug presence detect smi status (hppdm) ? r/wc. 1 = slsts.pdc (d28:f0/f1/f2/f3/f4/f5:5a, bit 3) transitioned from 0-to-1, and mpc.hpme (d28:f0/f1/f2/f3/f4/f5:d8, bit 1) is set. when this bit is set, an smi# will be generated. 0 power management smi status (pmms) ? r/wc. 1 = rsts.ps (d28:f0/f1/f2/f3/f4/f5:60, bit 16) transitioned from 0-to-1, and mpc.pmme (d28:f0/f1/f2/f3/f4/f5:d8, bit 1) is set. http://www..net/ datasheet pdf - http://www..net/ datasheet 755 pci express* configuration registers 20.1.51 rpdcgen?root port dy namic clock gating enable (pci express-d28:f0/f1/f2/f3/f4/f5) address offset: e1h attribute: r/w default value: 00h size: 8-bits 20.1.52 pecr1?pci express* configuration register 1 (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: e8h?ebh attribute: r/w default value: 00000020h size: 32 bits bits description 7:4 reserved. ro 3 shared resource dynamic link cl ock gating enable (srdlcgen) ? rw. 0 = disables dynamic clock gating of the shared resource link clock domain. 1 = enables dynamic clock gating on the root port shared resource link clock domain. only the value from port 1 is used for ports 1?4. only the value from port 5 is used for ports 5-6. 2 shared resource dynamic backbone clock gate enable (srdbcgen) ? rw. 0 = disables dynamic clock gating of the shared resource backbone clock domain. 1 = enables dynamic clock gating on the r oot port shared reso urce backbone clock domain. only the value from port 1 is used for ports 1?4. only the value from port 5 is used for ports 5-6. 1 root port dynamic link clock gate enable (rpdlcgen) ? rw. 0 = disables dynamic clock gating of the root port link clock domain. 1 = enables dynamic clock gating on the root port link clock domain. 0 root port dynamic backbone clock gate enable (rpdbcgen) ? rw. 0 = disables dynamic clock gating of th e root port backbone clock domain. 1 = enables dynamic clock gating on th e root port backbone clock domain. bit description 31:2 reserved 1 pecr1 field 2 ? r/w. bios may set this bit to 1. 0 reserved. http://www..net/ datasheet pdf - http://www..net/ pci express* configuration registers 756 datasheet 20.1.53 vch?virtual channel ca pability header register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 100h ? 103h attribute: rwo default value: 18010002h size: 32 bits 20.1.54 vcap2?virtual channe l capability 2 register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 108h ? 10bh attribute: ro default value: 00000001h size: 32 bits 20.1.55 pvc?port virtual ch annel control register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 10ch ? 10dh attribute: r/w default value: 0000h size: 16 bits bit description 31:20 next capability offset (nco) ? r/wo. indicates the next item in the list. 000h = does not support root comp lex topology capability structure. 180h = supports root complex topology capability structure. 19:16 capability version (cv) ? r/wo. indicates the version of the capability structure by the pci sig. 0h = does not support pci express virtual channel capability and the root complex topology capability structure. 1h = supports pci express virtual channel ca pability and the root complex topology capability structure. 15:0 capability id (cid) ? r/wo. indicates this is the virtual channel ca pability item. 0000h = does not support pci express virt ual channel capability and the root complex topology ca pability structure. 0002h = supports pci express virtual channel capability and the root complex topology capability structure. bit description 31:24 vc arbitration table offset (ato) ? ro. indicates that no table is present for vc arbitration since it is fixed. 23:0 reserved. bit description 15:4 reserved. 3:1 vc arbitration select (as) ? r/w. indicates which vc should be programmed in the vc arbitration table. the root port takes no action on the setting of this field since there is no arbitration table. 0 load vc arbitration table (lat) ? r/w. indicates that the table programmed should be loaded into the vc arbitration ta ble. this bit always returns 0 when read. http://www..net/ datasheet pdf - http://www..net/ datasheet 757 pci express* configuration registers 20.1.56 pvs?port virtual channel status register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 10eh ? 10fh attribute: ro default value: 0000h size: 16 bits 20.1.57 v0cap?virtual channel 0 re source capability register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 110h ? 113h attribute: ro default value: 00000001h size: 32 bits bit description 15:1 reserved. 0 vc arbitration table status (vas) ? ro. indicates the coherency status of the vc arbitration table when it is be ing updated. this fi eld is always 0 in the root port since there is no vc arbitration table. bit description 31:24 port arbitration table offset (at) ? ro. this vc implements no port arbitration table since the arbitration is fixed. 23 reserved. 22:16 maximum time slots (mts) ? ro. this vc implements fixed arbitration; therefore, this field is not used. 15 reject snoop transactions (rts) ? ro. this vc must be able to take snoopable transactions. 14 advanced packet switching (aps) ? ro. this vc is capable of all transactions, not just advanced packet switching transactions. 13:8 reserved. 7:0 port arbitration capability (pac) ? ro. indicates that this vc uses fixed port arbitration. http://www..net/ datasheet pdf - http://www..net/ pci express* configuration registers 758 datasheet 20.1.58 v0ctl?virtual channel 0 resource control register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 114h ? 117h attribute: r/w, ro default value: 800000ffh size: 32 bits 20.1.59 v0sts?virtual channel 0 resource status register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 11ah ? 11bh attribute: ro default value: 0000h size: 16 bits bit description 31 virtual channel enable (en) ? ro. always set to 1. virtual channel 0 cannot be disabled. 30:27 reserved. 26:24 virtual channel identifier (vcid) ? ro. indicates the id to use for this virtual channel. 23:20 reserved. 19:17 port arbitration select (pas) ? r/w. indicates which port table is being programmed. the root complex takes no action on this setting since the arbitration is fixed and there is no arbitration table. 16 load port arbitration table (lat) ? ro. the root port does not implement an arbitration table for this virtual channel. 15:8 reserved. 7:1 transaction class / virtual channel map (tvm) ? r/w. indicates which transaction classes are mapped to this virtual channel. when a bit is set, this transaction class is mapped to the virtual channel. 0 reserved. transaction class 0 must always mapped to vc0. bit transaction class 7 transaction class 7 6 transaction class 6 5 transaction class 5 4 transaction class 4 3 transaction class 3 2 transaction class 2 1 transaction class 1 bit description 15:2 reserved. 1 vc negotiation pending (np) ? ro. 0 = negotiation is not pending. 1 = indicates the virtual channel is still being negotiated with ingress ports. 0 port arbitration tables status (ats) . there is no port arbitration table for this vc, so this bit is reserved as 0. http://www..net/ datasheet pdf - http://www..net/ datasheet 759 pci express* configuration registers 20.1.60 ues?uncorrectable error status register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 144h ? 147h attribute: r/wc, ro default value: 00000000000x0xxx0x0x0000000x0000b size: 32 bits this register maintains its state through a platform reset. it loses its state upon suspend. bit description 31:21 reserved 20 unsupported request error status (ure) ? r/wc. indicates an unsupported request was received. 19 ecrc error status (ee) ? ro. ecrc is not supported. 18 malformed tlp status (mt) ? r/wc. indicates a malformed tlp was received. 17 receiver overflow status (ro) ? r/wc. indicates a rece iver overflow occurred. 16 unexpected completion status (uc) ? r/wc. indicates an unexpected completion was received. 15 completion abort status (ca) ? r/wc. indicates a completer abort was received. 14 completion timeout status (ct) ? r/wc. indicates a completion timed out. this bit is set if completion timeout is enabled and a completion is not returned within the time specified by the completion timeout value 13 flow control protocol error status (fcpe) ? ro. flow control protocol errors not supported. 12 poisoned tlp status (pt) ? r/wc. indicates a poisoned tlp was received. 11:5 reserved 4 data link protocol error status (dlpe) ? r/wc. indicates a data link protocol error occurred. 3:1 reserved 0 training error status (te) ? ro. training errors not supported. http://www..net/ datasheet pdf - http://www..net/ pci express* configuration registers 760 datasheet 20.1.61 uem?uncorrec table error mask (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 148h ? 14bh attribute: r/wo, ro default value: 00000000h size: 32 bits when set, the corresponding error in the ue s register is masked, and the logged error will cause no action. when cleared, the corresponding error is enabled. bit description 31:21 reserved 20 unsupported request error mask (ure) ? r/wo. 0 = the corresponding error in the ues re gister (d28:f0/f1/f2/f3/f4/f5:144) is enabled. 1 = the corresponding error in the ues re gister (d28:f0/f1/f2/f3/f4/f5:144) is masked. 19 ecrc error mask (ee) ? ro. ecrc is not supported. 18 malformed tlp mask (mt) ? r/wo. 0 = the corresponding error in the ues re gister (d28:f0/f1/f2/f3/f4/f5:144) is enabled. 1 = the corresponding error in the ues re gister (d28:f0/f1/f2/f3/f4/f5:144) is masked. 17 receiver overflow mask (ro) ? r/wo. 0 = the corresponding error in the ues re gister (d28:f0/f1/f2/f3/f4/f5:144) is enabled. 1 = the corresponding error in the ues re gister (d28:f0/f1/f2/f3/f4/f5:144) is masked. 16 unexpected completion mask (uc) ? r/wo. 0 = the corresponding error in the ues re gister (d28:f0/f1/f2/f3/f4/f5:144) is enabled. 1 = the corresponding error in the ues re gister (d28:f0/f1/f2/f3/f4/f5:144) is masked. 15 completion abort mask (ca) ? r/wo. 0 = the corresponding error in the ues re gister (d28:f0/f1/f2/f3/f4/f5:144) is enabled. 1 = the corresponding error in the ues re gister (d28:f0/f1/f2/f3/f4/f5:144) is masked. 14 completion timeout mask (ct) ? r/wo. 0 = the corresponding error in the ues re gister (d28:f0/f1/f2/f3/f4/f5:144) is enabled. 1 = the corresponding error in the ues re gister (d28:f0/f1/f2/f3/f4/f5:144) is masked. 13 flow control protocol error mask (fcpe) ? ro. flow control protocol errors not supported. 12 poisoned tlp mask (pt) ? r/wo. 0 = the corresponding error in the ues re gister (d28:f0/f1/f2/f3/f4/f5:144) is enabled. 1 = the corresponding error in the ues re gister (d28:f0/f1/f2/f3/f4/f5:144) is masked. 11:5 reserved http://www..net/ datasheet pdf - http://www..net/ datasheet 761 pci express* configuration registers 20.1.62 uev ? uncorrectable error severity (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 14ch ? 14fh attribute: ro default value: 00060011h size: 32 bits 4 data link protocol error mask (dlpe) ? r/wo. 0 = the corresponding error in the ues re gister (d28:f0/f1/f2/f3/f4/f5:144) is enabled. 1 = the corresponding error in the ues re gister (d28:f0/f1/f2/f3/f4/f5:144) is masked. 3:1 reserved 0 training error mask (te) ? ro. training errors not supported bit description bit description 31:21 reserved 20 unsupported request error severity (ure) ? ro. 0 = error considered non-fatal. (default) 1 = error is fatal. 19 ecrc error severity (ee) ? ro. ecrc is not supported. 18 malformed tlp severity (mt) ? ro. 0 = error considered non-fatal. 1 = error is fatal. (default) 17 receiver overflow severity (ro) ? ro. 0 = error considered non-fatal. 1 = error is fatal. (default) 16 unexpected completion severity (uc) ? ro. 0 = error considered non-fatal. (default) 1 = error is fatal. 15 completion abort severity (ca) ? ro. 0 = error considered non-fatal. (default) 1 = error is fatal. 14 completion timeout severity (ct) ? ro. 0 = error considered non-fatal. (default) 1 = error is fatal. 13 flow control protocol error severity (fcpe) ? ro. flow control protocol errors not supported. 12 poisoned tlp severity (pt) ? ro. 0 = error considered non-fatal. (default) 1 = error is fatal. 11:5 reserved 4 data link protocol error severity (dlpe) ? ro. 0 = error considered non-fatal. 1 = error is fatal. (default) 3:1 reserved 0 training error severity (te) ? ro. te is not supported. http://www..net/ datasheet pdf - http://www..net/ pci express* configuration registers 762 datasheet 20.1.63 ces ? correctable error status register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 150h ? 153h attribute: r/wc default value: 00000000h size: 32 bits 20.1.64 cem ? correctable error mask register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 154h ? 157h attribute: r/wo default value: 00000000h size: 32 bits when set, the corresponding error in the ce s register is masked, and the logged error will cause no action. when cleared, the corresponding error is enabled. bit description 31:14 reserved 13 advisory non-fatal error status (anfes) ? r/wc. 0 = advisory non-fatal error did not occur. 1 = advisory non-fatal error did occur. 12 replay timer timeout status (rtt) ? r/wc. indicates the replay timer timed out. 11:9 reserved 8 replay number rollover status (rnr) ? r/wc. indicates the replay number rolled over. 7 bad dllp status (bd) ? r/wc. indicates a bad dllp was received. 6 bad tlp status (bt) ? r/wc. indicates a bad tlp was received. 5:1 reserved 0 receiver error status (re) ? r/wc. indicates a re ceiver error occurred. bit description 31:14 reserved 13 advisory non-fatal error mask (anfem) ? r/wo. 0 = does not mask advisory non-fatal errors. 1 = masks advisory non-fatal errors from (a ) signaling err_cor to the device control register and (b) updating the unco rrectable error status register. this register is set by defa ult to enable compatibility wi th software that does not comprehend role-based error reporting. note: the correctable error detected bit in device status register is set whenever the advisory non-fatal error is detect ed, independent of this mask bit. 12 replay timer timeout mask (rtt) ? r/wo. mask for replay timer timeout. 11:9 reserved 8 replay number rollover mask (rnr) ? r/wo. mask for replay number rollover. 7 bad dllp mask (bd) ? r/wo. mask for bad dllp reception. 6 bad tlp mask (bt) ? r/wo. mask for bad tlp reception. 5:1 reserved 0 receiver error mask (re) ? r/wo. mask for receiver errors. http://www..net/ datasheet pdf - http://www..net/ datasheet 763 pci express* configuration registers 20.1.65 aecc ? advanced error capabilities and control register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 158h ? 15bh attribute: ro default value: 00000000h size: 32 bits 20.1.66 res ? root erro r status register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 170h ? 173h attribute: r/wc, ro default value: 00000000h size: 32 bits 20.1.67 rctcl ? root complex topology capability list register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 180 ? 183h attribute: ro default value: 00010005h size: 32 bits bit description 31:9 reserved 8 ecrc check enable (ece) ? ro. ecrc is not supported. 7 ecrc check capable (ecc) ? ro. ecrc is not supported. 6 ecrc generation enable (ege) ? ro. ecrc is not supported. 5 ecrc generation capable (egc) ? ro. ecrc is not supported. 4:0 first error pointer (fep) ? ro. bit description 31:27 advanced error interrupt message number (aemn) ? ro. there is only one error interrupt allocated. 26:4 reserved 3 multiple err_fatal/nonfatal received (menr) ? ro. for intel ? ich10, only one error will be captured. 2 err_fatal/nonfatal received (enr) ? r/wc. 0 = no error message received. 1 = either a fatal or a non-fata l error message is received. 1 multiple err_cor received (mcr) ? ro. for ich10, only one error will be captured. 0 err_cor received (cr) ? r/wc. 0 = no error message received. 1 = a correctable error message is received. bit description 31:20 next capability (next) ? ro. indicates the next item in the list, in this case, end of list. 19:16 capability version (cv) ? ro. indicates the version of the capability structure. 15:0 capability id (cid) ? ro. indicates this is a root complex topology capability. http://www..net/ datasheet pdf - http://www..net/ pci express* configuration registers 764 datasheet 20.1.68 esd?element self description register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 184h ? 187h attribute: ro default value: see description size: 32 bits 20.1.69 uld ? upstream link description register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 190h ? 193h attribute: ro default value: 00000001h size: 32 bits bit description 31:24 port number (pn) ? ro. indicate the ingress port nu mber for the root port. there is a different value per port: 23:16 component id (cid) ? ro. this field returns the valu e of the esd.cid field (chipset config space: offset 0104h:bits 23:16) of the chip configuration section, that is programmed by platform bios, since the root port is in the sa me component as the rcrb. 15:8 number of link entries (nle) ? ro. the default value of 01h indicates one link entry (corresponding to the rcrb). 7:4 reserved. 3:0 element type (et) ? ro. the default value of 0h indicates that the element type is a root port. port # value 1 01h 2 02h 3 03h 4 04h 5 05h 6 06h bit description 31:24 target port number (pn) ? ro. indicates the po rt number of the rcrb. 23:16 target component id (tcid) ? ro. this field returns th e value of the esd.cid field (chipset config space: offset 0104h:bits 23:16) of the chip configuration section, that is programmed by platform bios, since the ro ot port is in the sa me component as the rcrb. 15:2 reserved. 1 link type (lt) ? ro. indicates that the link points to the intel ? ich10 rcrb. 0 link valid (lv) ? ro. indicates that this link entry is valid. http://www..net/ datasheet pdf - http://www..net/ datasheet 765 pci express* configuration registers 20.1.70 ulba ? upstream link base address register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 198h ? 19fh attribute: ro default value: see description size: 64 bits 20.1.71 pecr2 ? pci express* configuration register 2 (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 300-303h attribute: r/w default value: 60005007h size: 32 bits 20.1.72 peetm ? pci ex press* extended te st mode register (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 318h attribute: ro default value: see description size: 8 bits bit description 63:32 base address upper (bau) ? ro. the rcrb of the intel ? ich10 lives in 32-bit space. 31:0 base address lower (bal) ? ro. this field matches the rcba register (d31:f0:offset f0h) va lue in the lpc bridge. bit description 31:20 reserved 21 pecr2 field 1 ? r/w. bios must set this bit to 1b. 20:0 reserved bit description 7:3 reserved 2 scrambler bypass mode (bau) ? r/w. 0 = normal operation. scrambler and descrambler are used. 1 = bypasses the data scrambler in the transmit direction and the data de-scrambler in the receive direction. note: this functionality intended for debug/testing only. note: if bypassing scrambler with ich10 root po rt 1 in x4 configuration, each ich10 root port must have this bit set. 1:0 reserved http://www..net/ datasheet pdf - http://www..net/ pci express* configuration registers 766 datasheet 20.1.73 pec1 ? pci express* configuration register 1 (pci express?d28:f0/f1/f2/f3/f4/f5) address offset: 324h attribute: ro, r/w default value: 14000016h size: 32 bits bit description 31:8 reserved 7:0 pec1 field 1 ? r/w. bios must program this field to 40h. http://www..net/ datasheet pdf - http://www..net/ datasheet 767 high precision event timer registers 21 high precision event timer registers the timer registers are memory-mapped in a non-indexed scheme. this allows the processor to directly access each register without having to use an index register. the timer register space is 1024 bytes. the registers are generally aligned on 64-bit boundaries to simplify implementation with ia64 processors. there are four possible memory address ranges beginning at 1) fed0_0000h, 2) fed0_1000h, 3) fed0_2000h, 4) fed0_3000h. the choice of address range will be selected by configuration bits in the high precision timer configuration register (chipset config registers:offset 3404h). behavioral rules: 1. software must not attempt to read or write across register boundaries. for example, a 32-bit access should be to offs et x0h, x4h, x8h, or xch. 32-bit accesses should not be to 01h, 02h, 03h, 05h, 06h, 07h, 09h, 0ah, 0bh, 0dh, 0eh, or 0fh. any accesses to these offsets will result in an unexpected behavior, and may result in a master abort. however, these accesses should not result in system hangs. 64- bit accesses can only be to x0h and must not cross 64-bit boundaries. 2. software should not write to read-only registers. 3. software should not expect any partic ular or consistent value when reading reserved registers or bits. 21.1 memory mapped registers table 21-1. memory-mapped registers (sheet 1 of 2) offset mnemonic register default type 000?007h gcap_id general capabilities and identification 0429b17f8 086a201h ro 008?00fh ? reserved ? ? 010?017h gen_conf general configuration 00000000 00000000h r/w 018?01fh ? reserved ? ? 020?027h gintr_sta general interrupt status 00000000 00000000h r/wc, r/ w 028?0efh ? reserved ? ? 0f0?0f7h main_cnt main counter value n/a r/w 0f8?0ffh ? reserved ? ? 100?107h tim0_conf timer 0 configuration and capabilities n/a r/w, ro 108?10fh tim0_comp timer 0 comparator value n/a r/w 110?11fh ? reserved ? ? 120?127h tim1_conf timer 1 configuration and capabilities n/a r/w, ro http://www..net/ datasheet pdf - http://www..net/ high precision event timer registers 768 datasheet notes: 1. reads to reserved registers or bits will return a value of 0. 2. software must not at tempt locks to the memory-mapped i/o ranges for high precision event timers. if attempted, the lock is not honored, wh ich means potential deadlock conditions may occur. 128?12fh tim1_comp timer 1 comparator value n/a r/w 130?13fh ? reserved ? ? 140?147h tim2_conf timer 2 configuration and capabilities n/a r/w, ro 148?14fh tim2_comp timer 2 comparator value n/a r/w 150?15fh ? reserved ? ? 160?167h tim3_cong timer 3 configuration and capabilities n/a r/w, ro 168?16fh tim3_comp timer 3 comparator value n/a r/w 170?3ffh (consumer only) ? reserved ? ? 180?187h (corporate only) tim4_cong timer 4 configuration and capabilities n/a r/w, ro 188?18fh (corporate only) tim4_comp timer 4 comparator value n/a r/w 190?19fh (corporate only) ? reserved ? ? 1a0?1a7h (corporate only) tim5_cong timer 5 configuration and capabilities n/a r/w, ro 1a8?1afh (corporate only) tim5_comp timer 5 comparator value n/a r/w 1b0?1bfh (corporate only) ? reserved ? ? 1c0?1c7h (corporate only) tim6_cong timer 6 configuration and capabilities n/a r/w, ro 1c8?1cfh (corporate only) tim6_comp timer 6 comparator value n/a r/w 1d0?1dfh (corporate only) ? reserved ? ? 1e0?1e7h (corporate only) tim7_cong timer 7 configuration and capabilities n/a r/w, ro 1e8?1efh (corporate only) tim7_comp timer 7 comparator value n/a r/w 1f0?19fh (corporate only) ? reserved ? ? 200?3ffh (corporate only) ? reserved ? ? table 21-1. memory-mapped registers (she et 2 of 2) offset mnemonic register default type http://www..net/ datasheet pdf - http://www..net/ datasheet 769 high precision event timer registers 21.1.1 gcap_id?general capabilitie s and identification register address offset: 00h attribute: ro default value: 0429b17f8086a201h size: 64 bits bit description 63:32 main counter tick period (counter_clk_per_cap) ? ro. this field indicates the period at which the counter increments in femptoseconds (10^-15 seconds). this will return 0429b17f when read. this indicates a period of 69841279 fs (69.841279 ns). 31:16 vendor id capabili ty (vendor_id_cap) ? ro. this is a 16-bit value assigned to intel. 15 legacy replacement rout capable (leg_rt_cap) ? ro. hardwired to 1. legacy replacement interrupt rout option is supported. 14 reserved. this bit returns 0 when read. 13 counter size capability (count_size_cap) ? ro. hardwired to 1. counter is 64-bit wide. 12:8 number of timer capability (num_tim_cap) ? ro. this field indicates the number of timers in this block. 03h = four timers. (consumer only) 07h = eight timers. (corporate only) 7:0 revision identification (rev_id) ? ro. this indicates which revision of the function is implemented. default value will be 01h. http://www..net/ datasheet pdf - http://www..net/ high precision event timer registers 770 datasheet 21.1.2 gen_conf?general configuration register address offset: 010h attribute: r/w default value: 00000000 00000000h size: 64 bits 21.1.3 gintr_sta?general interrupt status register address offset: 020h attribute: r/w, r/wc default value: 00000000 00000000h size: 64 bits . bit description 63:2 reserved. these bits return 0 when read. 1 legacy replacement rout (leg_rt_cnf) ? r/w. if the enable_cnf bit and the leg_rt_cnf bit are both set, then the interrupts will be routed as follows: ? timer 0 is routed to irq0 in 8259 or irq2 in the i/o apic ? timer 1 is routed to irq8 in 8259 or irq8 in the i/o apic ? timer 2-n is routed as per the rout ing in the timer n config registers. ? if the legacy replacement rout bit is set, the individual routing bits for timers 0 and 1 (apic) will have no impact. ? if the legacy replacement rout bit is not se t, the individual rout ing bits for each of the timers are used. ? this bit will default to 0. bios can set it to 1 to enable the legacy replacement routing, or 0 to disable th e legacy replacement routing. 0 overall enable (enable_cnf) ? r/w. this bit must be set to enable any of the timers to generate interrupts. if this bit is 0, then the main counter will halt (will not increment) and no interrupts will be caused by any of these timers. for level-triggered interrupts, if an interrupt is pending when the enable_cnf bit is changed from 1 to 0, the interrupt status in dications (in the various txx_int_sts bits) will not be cleared. software must write to the txx_in t_sts bits to clear the interrupts. note: this bit will default to 0. bios can set it to 1 or 0. bit description 63:8 reserved. these bits wi ll return 0 when read. 7 (corporate only) timer 7interrupt active (t07_int_sts) ? r/w. same functionality as timer 0. 6 (corporate only) timer 6interrupt active (t06_int_sts) ? r/w. same functionality as timer 0. 5 (corporate only) timer 5interrupt active (t05_int_sts) ? r/w. same functionality as timer 0. 4 (corporate only) timer 4interrupt active (t04_int_sts) ? r/w. same functionality as timer 0. 7:4 (consumer only) reserved. these bits will return 0 when read. 3 timer 3interrupt active (t03_int_sts) ? r/w. same functionality as timer 0. http://www..net/ datasheet pdf - http://www..net/ datasheet 771 high precision event timer registers 21.1.4 main_cnt?main co unter value register address offset: 0f0h attribute: r/w default value: n/a size: 64 bits . 2 timer 2 interrupt active (t02_int_sts) ? r/w. same func tionality as timer 0. 1 timer 1 interrupt active (t01_int_sts) ? r/w. same func tionality as timer 0. 0 timer 0 interrupt active (t00_int_sts) ? r/wc. the functionality of this bit depends on whether the edge or level-triggered mode is used for this timer. (default = 0) if set to level-triggered mode: this bit will be set by hardware if th e corresponding timer interrupt is active. once the bit is set, it ca n be cleared by software writing a 1 to the same bit position. writes of 0 to this bit will have no effect. if set to edge-triggered mode: this bit should be ignored by software. software should always write 0 to this bit. note: defaults to 0. in edge triggered mode , this bit will always read as 0 and writes will have no effect. bit description bit description 63:0 counter value (counter_val[63:0]) ? r/w. reads return the current value of the counter. writes load the new value to the counter. notes: 1. writes to this register should only be done while the counter is halted. 2. reads to this register return th e current value of the main counter. 3. 32-bit counters will always return 0 for the upper 32-bits of this register. 4. if 32-bit software attempts to read a 64-bit counter, it should first halt the counter. since this delays th e interrupts for all of the ti mers, this should be done only if the consequences are understood. it is strongly recommended that 32-bit software only operate th e timer in 32-bit mode. 5. reads to this register are monotonic. no two consecutive reads return the same value. the second of two reads always returns a larger value (unless the timer has rolled over to 0). http://www..net/ datasheet pdf - http://www..net/ high precision event timer registers 772 datasheet 21.1.5 timn_conf?timer n configuration and capabilities register address offset: timer 0: 100?107h attribute: ro, r/w timer 1: 120?127h timer 2: 140?147h timer 3: 160?167h timer 4: 180?187h (corporate only) timer 5: 1a0?1a7h (corporate only) timer 6: 1c0?1c7h (corporate only) timer 7: 1e0?1e7h (corporate only) default value: n/a size: 64 bit note: the letter n can be 0, 1, 2, 3, 4, 5, 6, or 7 (4, 5, 6, 7 corporate only) referring to timer 0, 1, 2, 3, 4, 5, 6, or 7(4,5,6,7 corporate only). bit description 63:56 reserved. these bits will return 0 when read. 55:52, 43 timer interrupt rout capabi lity (timern_int_rout_cap) ? ro. timer 0, 1: bits 52, 53, 54, and 55 in this field (corresponding to irq 20, 21, 22, and 23) have a value of 1. wr ites will have no effect. timer 2: bits 43, 52, 53, 54, and 55 in this field (corresponding to irq 11, 20, 21, 22, and 23) have a value of 1. writes will have no effect. timer 3: bits 44, 52, 53, 54, and 55 in this field (corresponding to irq 11, 20, 21, 22, and 23) have a value of 1. writes will have no effect. timer 4, 5, 6, 7 (corporate only). this field is always 0 as interrupts from these timers can only be delivered vi a direct fsb inte rrupt messages. note: if irq 11 is used for hpet #2, softwa re should ensure ir q 11 is not shared with any other devices to ensure the proper operation of hpet #2. note: if irq 12 is used for hpet #3, softwa re should ensure ir q 12 is not shared with any other devices to ensure the proper operation of hpet #3. 51:45, 42:16 reserved . these bits return 0 when read. 15 (corporate only) timern_fsb_int_del_cap: fsb interrupt delivery: (where n is the timer number: 00 to 07). if this read-only bit is 1, then the hardwa re supports a direct front-side bus delivery of this timer?s interrupt. intel specific: this bit is always re ad as 1, since the intel ich10 hpet implementation supports the di rect fsb interru pt delivery. 15 (consumer only) reserved . this bit returns 0 when read. 14 (corporate only) timern_fsb_en_cnf: (where n is the timer number: 00 to 07). if the timern_fsb_int_del_cap bit is set for this timer, then the software can set the timern_fsb_en_cnf bit to force the interr upts to be delivered directly as fsb messages, rather than using the 8259 or i/o (x) apic. in this case, the timern_int_rout_cnf field in this register will be ignored. the timern_fsb_rout register will be used instead. intel and timer 0, 1, 2, 3 specif ic: this bit is a read/write bit. intel and timer 4, 5, 6, 7 specific: this bit is always read only 1 as interrupt from these timers can only be delivered via direct fsb interrupt messages. 14 (consumer only) reserved . this bit returns 0 when read. http://www..net/ datasheet pdf - http://www..net/ datasheet 773 high precision event timer registers 13:9 interrupt rout (timern_int_rout_cnf) ? r/w. this 5-bit field indicates the routing for the interrupt to the 8259 or i/o (x) apic. software writes to this field to select which interrupt in the 8259 or i/o (x) will be used for this timer?s interrupt. if the value is not supported by this particular timer, then the value read back will not match what is written. th e software must only write valid values. timer 4, 5, 6, 7 (corporate only): this field is read-only and reads will return 0. notes: 1. if the interrupt is handled via the 8 259, only interrupts 0-15 are applicable and valid. software must not progra m any value other than 0-15 in this field. 2. if the legacy replacement rout bit is set, then timers 0 and 1 will have a different routing, and th is bit field has no effect for those two timers. 3. timer 0,1: software is responsible to make sure it programs a valid value (20, 21, 22, or 23) for this field. the ich10 logic does not check the validity of the value written. 4. timer 2: software is responsible to ma ke sure it programs a valid value (11, 20, 21, 22, or 23) for this field. the ich10 logic does not check the validity of the value written. 5. timer 3: software is responsible to ma ke sure it programs a valid value (12, 20, 21, 22, or 23) for this field. the ich10 logic does not check the validity of the value written. 8 timer n 32-bit mode (timern_32mode_cnf) ? r/w or ro. software can set this bit to force a 64-bit timer to behave as a 32-bit timer. timer 0: bit is read/write (default to 0). 0 = 64 bit; 1 = 32 bit timers 1, 2, 3, 4, 5, 6, 7 (4, 5, 6, 7 co rporate only): hardwire d to 0. writes have no effect (since these two timers are 32-bits). note: when this bit is set to 1, the hardware counter will do a 32-bit operation on comparator match and ro llovers, thus the uppe r 32-bit of the timer 0 comparator value register is ignored. the upper 32-bit of the main counter is not involved in any rollover from lower 32-bit of the main counter and becomes all zeros. 7 reserved . this bit returns 0 when read. 6 timer n value set (timern_val_set_cnf) ? r/w. software uses this bit only for timer 0 if it has been set to peri odic mode. by writing this bit to a 1, the software is then allowed to directly set the timer?s ac cumulator. software does not have to write this bit back to 1 (it automatically clears). software should not write a 1 to this bit position if the timer is set to non-periodic mode. note: this bit will return 0 when read. writes will only have an effect for timer 0 if it is set to periodic mode. writes will have no effect for timers 1, 2, 3, 4, 5, 6, 7 (4, 5, 6, 7 corporate only). 5 timer n size (timern_size_cap) ? ro. this read only field indicates the size of the timer. timer 0: value is 1 (64-bits). timers 1, 2, 3, 4, 5, 6, 7 (4, 5, 6, 7 corporate only): value is 0 (32-bits). 4 periodic interrupt capa ble (timern_per_int_cap) ? ro. if this bit is 1, the hardware supports a periodic mode for this timer?s interrupt. timer 0: hardwired to 1 (suppo rts the periodic interrupt). timers 1, 2, 3, 4, 5, 6, 7 (4, 5, 6, 7 corporate only): hardwired to 0 (does not support periodic interrupt). bit description http://www..net/ datasheet pdf - http://www..net/ high precision event timer registers 774 datasheet note: reads or writes to unimplemented timers should not be attempted. read from any unimplemented registers will re turn an undetermined value. 3 timer n type (timern_type_cnf) ? r/w or ro. timer 0: bit is read/write. 0 = disable ti mer to generate periodic interrupt; 1 = enable timer to generate a periodic interrupt. timers 1, 2, 3, 4, 5, 6, 7 (4, 5, 6, 7 co rporate only): hardwired to 0. writes have no affect. 2 timer n interrupt enable (timern_int_enb_cnf) ? r/w. this bit must be set to enable timer n to cause an interrupt when it times out. 0 = disable (default). the timer can sti ll count and generate appropriate status bits, but will not cause an interrupt. 1 = enable. 1 timer interrupt type (timern_int_type_cnf) ? r/w. 0 = the timer interrupt is e dge triggered. this means th at an edge-type interrupt is generated. if another interrupt occurs, another edge will be generated. 1 = the timer interrupt is level triggere d. this means that a level-triggered interrupt is generated. the interrupt will be held active until it is cleared by writing to the bit in the general interrupt status register. if another interrupt occurs before the interrupt is cleared, the interru pt will remain active. timer 4, 5, 6, 7 (4, 5, 6, 7 corporate only ): this bit is read-only, and will return 0 when read 0 reserved . these bits will return 0 when read. bit description http://www..net/ datasheet pdf - http://www..net/ datasheet 775 high precision event timer registers 21.1.6 timn_comp?timer n co mparator value register address offset: timer 0: 108h?10fh timer 1: 128h?12fh timer 2: 148h?14fh timer 3: 168h?16fh timer 4: 188h ? 18fh (corporate only) timer 5: 1a8h ? 1afh (corporate only) timer 6: 1c8h ? 1cfh (corporate only) timer 7: 1e8h ? 1efh (corporate only) attribute: r/w default value: n/a size: 64 bit bit description 63:0 timer compare value ? r/w. reads to this register return the current value of the comparator timers 0, 1, 2, 3, 4, 5, 6, 7 (4, 5, 6, 7 corporate only) are configured to non-periodic mode: writes to this register load the value against which the main counter should be compared for this timer. ? when the main counter equals the valu e last written to this register, the corresponding interrupt can be generated (if so enabled). ? the value in this register does no t change based on the interrupt being generated. timer 0 is configured to periodic mode: ? when the main counter equals the valu e last written to this register, the corresponding interrupt can be generated (if so enabled). ? after the main counte r equals the value in this register, the value in this register is increased by the value last written to the register. for example, if the value written to the register is 00000123h, then 1. an interrupt will be generated wh en the main counter reaches 00000123h. 2. the value in this register will then be adjusted by the hardware to 00000246h. 3. another interrupt will be generated when the main counter reaches 00000246h 4. the value in this register will then be adjusted by the hardware to 00000369h ? as each periodic interrupt oc curs, the value in this register will increment. when the incremented value is greater than the maximum value possible for this register (ffffffffh for a 32-bit timer or ffffffffffffffffh for a 64-bit timer), the value will wrap around through 0. for example, if the current value in a 32-bit timer is ffff0000h and the last value writ ten to this register is 20000, then after the next interrupt the value will change to 00010000h default value for each timer is all 1s for th e bits that are implemented. for example, a 32-bit timer has a default value of 00000000ffffffffh. a 64-bit timer has a default value of ffffffffffffffffh. http://www..net/ datasheet pdf - http://www..net/ high precision event timer registers 776 datasheet http://www..net/ datasheet pdf - http://www..net/ datasheet 777 serial peripheral interface (spi) 22 serial peripheral interface (spi) the serial peripheral interface resides in me mory mapped space. this function contains registers that allow for the setup and programming of devices that reside on the spi interface. note: all registers in this function (including me mory-mapped registers) must be addressable in byte, word, and dword quantities. the software must always make register accesses on natural boundaries (i.e., dword accesses must be on dword boundaries; word accesses on word boundaries, etc.) in ad dition, the memory-mapped register space must not be accessed with the lock semantic exclusive-access mechanism. if software attempts exclusive-access mechanisms to the spi memory-mapped space, the results are undefined. 22.1 serial peripheral interface memory mapped configuration registers the spi host interface registers are memory-mapped in the rcrb (root complex register block) chipset register space with a base address (spibar) of 3800h and are located within the range of 3800h to 39ffh . the address for rcrb can be found in rcba register see section 13.1.36 . the individual registers are then accessible at spibar + offset as indicated table 22-1 . these memory mapped registers must be accessed in byte, word, or dword quantities. table 22-1. serial peripheral inte rface (spi) register address map (spi memory mapped configuratio n registers) (sheet 1 of 2) spibar + offset mnemonic register name default type 00h?03h bfpr bios flash primary region 00000000h ro 04h?05h hsfsts hardware sequencing flash status 0000h ro, r/wc, r/w 06h?07h hsfctl hardware sequencing flash control 0000h r/w, r/ws 08h?0bh faddr flash address 00000000h r/w 0ch?0fh reserved reserved 00000000h 10h?13h fdata0 flash data 0 00000000h r/w 14h?4fh fdatan flash data n 00000000h r/w 50h?53h fracc flash region access permissions 00000202h ro, r/w 54h?57h freg0 flash region 0 00000000h ro 58h?5bh freg1 flash region 1 00000000h ro 5ch?5f freg2 flash region 2 00000000h ro 60h?63h freg3 flash region 3 00000000h ro 64h?67h freg3 flash region 4 00000000h ro 67h?73h reserved reserved for future flash regions http://www..net/ datasheet pdf - http://www..net/ serial peripheral interface (spi) 778 datasheet 74h?77h fpr0 flash protected range 0 00000000h r/w 78h?7bh fpr1 flash protected range 1 00000000h r/w 7ch?7fh fpr2 flash protected range 2 00000000h r/w 80?83h fpr3 flash protected range 3 00000000h r/w 84h?87h fpr4 flash protected range 4 00000000h r/w 88h?8fh ? reserved ? 90h ssfsts software sequencing flash status 00h ro, r/wc 91h?93h ssfctl software sequencing flash control 0000h r/w 94h?95h preop prefix opcode configuration 0000h r/w 96h?97h optype opcode type configuration 0000h r/w 98h?9fh opmenu opcode menu configuration 00000000 00000000h r/w a0h bbar bios base address configuration 00000000h r/w, ro b0h?b3h fdoc flash descriptor observability control 00000000h r/w b4h?b7h fdod flash descriptor observability data 00000000h ro b8h?c3h ? reserved ? c0h?c3h afc additional flash control 00000000h ro, r/w c4?c7h lvscc host lower vendor specific component capabilities 00000000h ro, r/wl c8?c11h uvscc host upper vendor specific component capabilities 00000000h ro, r/wl d0?d3h fpb flash partition boundary 00000000h ro table 22-1. serial peripheral inte rface (spi) register address map (spi memory mapped configuration register s) (sheet 2 of 2) spibar + offset mnemonic register name default type http://www..net/ datasheet pdf - http://www..net/ datasheet 779 serial peripheral interface (spi) 22.1.1 bfpr ?bios flash pr imary region register (spi memory mapped configuration registers) memory address: spibar + 00h attribute: ro default value: 00000000h size: 32 bits note: this register is only applicable when spi device is in descriptor mode. 22.1.2 hsfs?hardware sequencing flash status register (spi memory mapped configuration registers) memory address: spibar + 04h attribute: ro, r/wc, r/w default value: 0000h size: 16 bits bit description 31:29 reserved 28:16 bios flash primary re gion limit (prl) ? ro. this specifies address bits 24:12 for the primary region limit. the value in this register loaded from the contents in the flash descriptor.flreg 1.region limit. 15:13 reserved 12:0 bios flash primary region base (prb) ? ro. this specifies address bits 24:12 for the primary region base the value in this register is load ed from the contents in the flash descriptor.flreg1.region base. bit description 15 flash configuration lock-down (flockdn) ? r/w/l. when set to 1, those flash program registers that are locked down by this flockdn bit cannot be written. once set to 1, this bit can only be cleared by a hardware reset du e to a global reset or host partition reset in an intel me enabled system. 14 flash descriptor valid (fdv) ? ro. this bit is set to a 1 if the flash controller read the correct flash descriptor signature. if the flash descriptor valid bit is not 1, software cannot use the hardware sequencing registers, but must use the software sequencing registers. any attempt to use the hardware sequencing registers will result in the fcerr bit being set. 13 flash descriptor override pin-strap status (fdopss) ? ro: this register reflects the value the flash descri ptor override pin-strap. 0 = the flash descriptor override strap is set 1 = no override 12:6 reserved 5 spi cycle in progress (scip)? ro. hardware sets this bi t when software sets the flash cycle go (fgo) bit in the hardware se quencing flash control register. this bit remains set until the cycle completes on the spi interface. hardware automatically sets and clears this bit so that software can dete rmine when read data is valid and/or when it is safe to begin programming the next command. software must only program the next command when this bit is 0. note: this field is only applicable when in descriptor mode and hardware sequencing is being used. http://www..net/ datasheet pdf - http://www..net/ serial peripheral interface (spi) 780 datasheet 4:3 block/sector eras e size (berase) ? ro. this field identifies the erasable sector size for all flash components. valid bit settings: 00 = 256 byte 01 = 4 k byte 10 = 8 k byte 11 = 64 k byte if the fla is less than fpba then this field reflects the value in the lvscc.lbes register. if the fla is greater or equal to fpba th en this field reflects the value in the uvscc.ubes register. note: this field is only applicable when in descriptor mode and hardware sequencing is being used. 2 access error log (ael) ? r/w/c. hardware sets this bit to a 1 when an attempt was made to access the bios regi on using the direct access method or an access to the bios program registers that violated the security restrictions. this bit is simply a log of an access security violat ion. this bit is cleared by software writing a 1. note: this field is only applicable when in descriptor mode and hardware sequencing is being used. 1 flash cycle error (fcerr) ? r/w/c. hardware sets this bit to 1 when an program register access is bl ocked to the flash due to one of the protection policies or when any of the programmed cycle re gisters is written while a programmed access is already in progress. this bit remains asserted until cleared by so ftware writing a 1 or until hardware reset occurs due to a global reset or host part ition reset in an intel me enabled system. software must clear this bit before se tting the flash cycle go bit in this register. note: this field is only applicable when in descriptor mode and hardware sequencing is being used. 0 flash cycle done (fdone) ? r/w/c. the ich sets this bit to 1 when the spi cycle completes after software previously set the fgo bit. this bit re mains asserted until cleared by software writing a 1 or hardware re set due to a global re set or host partition reset in an intel me enabled system. when this bit is set and the spi smi# enable bit is set, an internal signal is as serted to the smi# generation block. software must make sure this bit is cleared prior to enabling the spi smi# assertion for a new programmed access. note: this field is only applicable when in descriptor mode and hardware sequencing is being used. bit description http://www..net/ datasheet pdf - http://www..net/ datasheet 781 serial peripheral interface (spi) 22.1.3 hsfc?hardware sequencing flash control register (spi memory mapped configuration registers) memory address: spibar + 06h attribute: r/w, r/ws default value: 0000h size: 16 bits note: this register is only applicable when spi device is in descriptor mode. 22.1.4 faddr?flash address register (spi memory mapped configuration registers) memory address: spibar + 08h attribute: r/w default value: 00000000h size: 32 bits bit description 15 flash spi smi# enable (fsmie) ? r/w. when set to 1, the spi asserts an smi# request whenever the flash cycle done bit is 1. 14 reserved 13:8 flash data byte count (fdbc) ? r/w. this field specifies the number of bytes to shift in or out during the data portion of the spi cycle. the contents of this register are 0s based with 0b representing 1 byte and 111111b representing 64 bytes. the number of bytes transferred is the value of this field plus 1. this field is ignored for the block erase command. 7:3 reserved 2:1 flash cycle (fcycle) ? r/w. this field defines the flash spi cycle type generated to the flash when the fgo bi t is set as defined below: 00 = read (1 up to 64 bytes by setting fdbc) 01 = reserved 10 = write (1 up to 64 bytes by setting fdbc) 11 = block erase 0 flash cycle go (fgo) ? r/w/s. a write to this register with a 1 in this bit initiates a request to the flash spi arbiter to start a cy cle. this register is cleared by hardware when the cycle is granted by the spi arbiter to run the cycle on the spi bus. when the cycle is complete, the fdone bit is set. software is forbidden to write to any regist er in the hsflctl register between the fgo bit getting set and the fdone bi t being cleared. any attempt to violate this rule will be ignored by hardware. hardware allows other bits in this register to be progra mmed for the same transaction when writing this bit to 1. this saves an addition al memory write. this bit always returns 0 on reads. bit description 31:25 reserved 24:0 flash linear address (fla) ? r/w. the fla is the starting byte linear address of a spi read or write cycle or an address within a block for the block erase command. the flash linear address must fall within a regi on for which bios has access permissions. hardware must convert the fla into a flash physical address (fpa) before running this cycle on the spi bus. http://www..net/ datasheet pdf - http://www..net/ serial peripheral interface (spi) 782 datasheet 22.1.5 fdata0?flash data 0 register (spi memory mapped co nfiguration registers) memory address: spibar + 10h attribute: r/w default value: 00000000h size: 32 bits 22.1.6 fdatan?flash data [n] register (spi memory mapped co nfiguration registers) memory address: spibar + 14h attribute: r/w spibar + 18h spibar + 1ch spibar + 20h spibar + 24h spibar + 28h spibar + 2ch spibar + 30h spibar + 34h spibar + 38h spibar + 3ch spibar + 40h spibar + 44h spibar + 48h spibar + 4ch default value: 00000000h size: 32 bits bit description 31:0 flash data 0 (fd0) ? r/w. this field is shifted out as the spi data on the master-out slave-in data pin during the data portion of the spi cycle. this register also shifts in the data from th e master-in slave-out pin into this register during the data portion of the spi cycle. the data is always shifted starting with the least significant byte, msb to lsb, followed by the next least significant by te, msb to lsb, etc. specifically, the shift order on spi in terms of bits within this register is: 7-6-5-4-3-2-1-0-15-14-13-?8-23-22-?16-31?24 bit 24 is the last bit shifted out/in. there are no alignment assumptions; byte 0 always represents the value specified by the cycle address. note that the data in this register may be modified by the hardware during any programmed spi transaction. direct memory reads do not modify the contents of this register. bit description 31:0 flash data n (fd[n]) ? r/w. similar definition as flash data 0. however, this register does not begin shifting until fd[n-1] has completely shifted in/out.? r/w. http://www..net/ datasheet pdf - http://www..net/ datasheet 783 serial peripheral interface (spi) 22.1.7 frap?flash regions acce ss permissions register (spi memory mapped configuration registers) memory address: spibar + 50h attribute: ro, r/w default value: 00000202h size: 32 bits note: this register is only applicable when spi device is in descriptor mode. bit description 31:24 bios master write access grant (bmwag) ? r/w. each bit [31:29] corresponds to master[7:0]. bios can grant one or more masters write access to the bios region 1 overriding the permissions in the flash descriptor. master[1] is host processor/bios, master[2] is intel management engine, master[3] is host processor/gbe. master[0] and master[7:4] are reserved. the contents of this register are locked by the flockdn bit. 23:16 bios master read access grant (bmrag) ? r/w. each bit [28:16] corresponds to master[7:0]. bios can grant one or more ma sters read access to the bios region 1 overriding the read permissi ons in the flash descriptor. master[1] is host processor/bios, master[2] is intel management engine, master[3] is host processor/gbe. master[0] and master[7:4] are reserved. the contents of this register are locked by the flockdn bit 15:8 bios region write access (brwa) ? ro. each bit [15:8] corresponds to regions [7:0]. if the bit is set, this master can er ase and write that part icular region through register accesses. the contents of this register are that of the flash descri ptor. flash master 1 master region write access or a particular master has granted bios write permissions in their master write access grant register or the flash descriptor security override strap is set. 7:0 bios region read access (brra) ? ro. each bit [7:0] corresponds to regions [7:0]. if the bit is set, this master can re ad that particular re gion through register accesses. the contents of this register are that of the flash descri ptor.flash master 1.master region write access or a particular master has granted bios read permissions in their master read access grant regi ster or the flash descriptor security override strap is set. http://www..net/ datasheet pdf - http://www..net/ serial peripheral interface (spi) 784 datasheet 22.1.8 freg0?flash region 0 (f lash descriptor) register (spi memory mapped co nfiguration registers) memory address: spibar + 54h attribute: ro default value: 00000000h size: 32 bits note: this register is only applicable when spi device is in descriptor mode. 22.1.9 freg1?flash region 1 (bios descriptor) register (spi memory mapped co nfiguration registers) memory address: spibar + 58h attribute: ro default value: 00000000h size: 32 bits note: this register is only applicable when spi device is in descriptor mode. bit description 31:29 reserved 28:16 region limit (rl) ? ro. this specifies address bits 24:12 for the region 0 limit. the value in this register is load ed from the contents in the flash descriptor.flreg0.region limit 15:13 reserved 12:0 region base (rb) / flash descriptor base address region (fdbar) ? ro. this specifies address bits 24 :12 for the region 0 base the value in this register is load ed from the contents in the flash descriptor.flreg0.region base bit description 31:29 reserved 28:16 region limit (rl) ? ro. this specifies address bits 24:12 for the region 1 limit. the value in this register is load ed from the contents in the flash descriptor.flreg1.region limit 15:13 reserved 12:0 region base (rb) ? ro. this specifies address bits 24:12 for the region 1 base the value in this register is load ed from the contents in the flash descriptor.flreg1.region base http://www..net/ datasheet pdf - http://www..net/ datasheet 785 serial peripheral interface (spi) 22.1.10 freg2?flash regi on 2 (me) register (spi memory mapped configuration registers) memory address: spibar + 5ch attribute: ro default value: 00000000h size: 32 bits note: this register is only applicable when spi device is in descriptor mode. 22.1.11 freg3?flash regi on 3 (gbe) register (spi memory mapped configuration registers) memory address: spibar + 60h attribute: ro default value: 00000000h size: 32 bits note: this register is only applicable when spi device is in descriptor mode. bit description 31:29 reserved 28:16 region limit (rl) ? ro. this specifies address bits 24:12 for the region 2 limit. the value in this register is load ed from the contents in the flash descriptor.flreg 2.region limit 15:13 reserved 12:0 region base (rb) ? ro. this specifies address bits 24:12 for the region 2 base the value in this register is load ed from the contents in the flash descriptor.flreg2.region base bit description 31:29 reserved 28:16 region limit (rl) ? ro. this specifies address bits 24:12 for the region 3 limit. the value in this register is load ed from the contents in the flash descriptor.flreg 3.region limit 15:13 reserved 12:0 region base (rb) ? ro. this specifies address bits 24:12 for the region 3 base the value in this register is load ed from the contents in the flash descriptor.flreg3.region base http://www..net/ datasheet pdf - http://www..net/ serial peripheral interface (spi) 786 datasheet 22.1.12 freg4?flash region 4 (platform data) register (spi memory mapped co nfiguration registers) memory address: spibar + 64h attribute: ro default value: 00000000h size: 32 bits note: this register is only applicable when spi device is in descriptor mode. 22.1.13 pr0?protected range 0 register (spi memory mapped co nfiguration registers) memory address: spibar + 74h attribute: r/w default value: 00000000h size: 32 bits note: this register can not be written when the flockdn bit is set to 1. bit description 31:29 reserved 28:16 region limit (rl) ? ro. this specifies address bits 24:12 for the region 4 limit. the value in this register is load ed from the contents in the flash descriptor.flreg4.region limit 15:13 reserved 12:0 region base (rb) ? ro. this specifies address bits 24:12 for the region 4 base the value in this register is load ed from the contents in the flash descriptor.flreg4.region base bit description 31 write protection enable ? r/w. when set, this bit indicates that the base and limit fields in this register are va lid and that writes and erases directed to addresses between them (inclusive) must be bl ocked by hardware. the base and limit fields are ignored when this bit is cleared. 30:29 reserved 28:16 protected range limit ? r/w. this field corresponds to fla address bits 24:12 and specifies the upper limit of th e protected range. address bi ts 11:0 are assumed to be fffh for the limit comparison. any address gr eater than the value programmed in this field is unaffected by this protected range. 15 read protection enable ? r/w. when set, this bit indicates that the base and limit fields in this register are valid and that read directed to a ddresses between them (inclusive) must be blocked by hardware. th e base and limit fiel ds are ignored when this bit is cleared. 14:13 reserved 12:0 protected range base ? r/w. this field corresponds to fla address bits 24:12 and specifies the lower base of the protected ra nge. address bits 11:0 are assumed to be 000h for the base comparison. any address less than the value programmed in this field is unaffected by this protected range. http://www..net/ datasheet pdf - http://www..net/ datasheet 787 serial peripheral interface (spi) 22.1.14 pr1?protected range 1 register (spi memory mapped configuration registers) memory address: spibar + 78h attribute: r/w default value: 00000000h size: 32 bits note: this register can not be written when the flockdn bit is set to 1. bit description 31 write protection enable ? r/w. when set, this bit indicates that the base and limit fields in this register are va lid and that writes and erases directed to addresses between them (inclusive) must be blocked by hardwa re. the base and limit fields are ignored when this bit is cleared. 30:29 reserved 28:16 protected range limit ? r/w. this field corresponds to fla address bits 24:12 and specifies the upper limit of th e protected range. address bi ts 11:0 are assumed to be fffh for the limit comparison. any address gr eater than the value programmed in this field is unaffected by this protected range. 15 read protection enable ? r/w. when set, this bit indicates that the base and limit fields in this register are valid and that read directed to a ddresses between them (inclusive) must be blocked by hardware. th e base and limit fields are ignored when this bit is cleared. 14:13 reserved 12:0 protected range base ? r/w. this field corresponds to fla address bits 24:12 and specifies the lower base of the protected ra nge. address bits 11: 0 are assumed to be 000h for the base comparison. any address less than the value programmed in this field is unaffected by this protected range. http://www..net/ datasheet pdf - http://www..net/ serial peripheral interface (spi) 788 datasheet 22.1.15 pr2?protected range 2 register (spi memory mapped co nfiguration registers) memory address: spibar + 7ch attribute: r/w default value: 00000000h size: 32 bits note: this register can not be written when the flockdn bit is set to 1. 22.1.16 pr3?protected range 3 register (spi memory mapped co nfiguration registers) memory address: spibar + 80h attribute: r/w default value: 00000000h size: 32 bits note: this register can not be written when the flockdn bit is set to 1. bit description 31 write protection enable ? r/w. when set, this bit indicates that the base and limit fields in this register are va lid and that writes and erases directed to addresses between them (inclusive) must be bl ocked by hardware. the base and limit fields are ignored when this bit is cleared. 30:29 reserved 28:16 protected range limit ? r/w. this field corresponds to fla address bits 24:12 and specifies the upper limit of th e protected range. address bi ts 11:0 are assumed to be fffh for the limit comparison. any address gr eater than the value programmed in this field is unaffected by this protected range. 15 read protection enable ? r/w. when set, this bit indicates that the base and limit fields in this register are valid and that read directed to a ddresses between them (inclusive) must be blocked by hardware. th e base and limit fiel ds are ignored when this bit is cleared. 14:13 reserved 12:0 protected range base ? r/w. this field corresponds to fla address bits 24:12 and specifies the lower base of the protected ra nge. address bits 11:0 are assumed to be 000h for the base comparison. any address less than the value programmed in this field is unaffected by this protected range. bit description 31 write protection enable ? r/w. when set, this bit indicates that the base and limit fields in this register are va lid and that writes and erases directed to addresses between them (inclusive) must be bl ocked by hardware. the base and limit fields are ignored when this bit is cleared. 30:29 reserved 28:16 protected range limit ? r/w. this field corresponds to fla address bits 24:12 and specifies the upper limit of th e protected range. address bi ts 11:0 are assumed to be fffh for the limit comparison. any address gr eater than the value programmed in this field is unaffected by this protected range. 15 read protection enable ? r/w. when set, this bit indicates that the base and limit fields in this register are valid and that read directed to a ddresses between them (inclusive) must be blocked by hardware. th e base and limit fiel ds are ignored when this bit is cleared. 14:13 reserved 12:0 protected range base ? r/w. this field corresponds to fla address bits 24:12 and specifies the lower base of the protected ra nge. address bits 11:0 are assumed to be 000h for the base comparison. any address less than the value programmed in this field is unaffected by this protected range. http://www..net/ datasheet pdf - http://www..net/ datasheet 789 serial peripheral interface (spi) 22.1.17 pr4?protected range 4 register (spi memory mapped configuration registers) memory address: spibar + 84h attribute: r/w default value: 00000000h size: 32 bits note: this register can not be written when the flockdn bit is set to 1. bit description 31 write protection enable ? r/w. when set, this bit indicates that the base and limit fields in this register are va lid and that writes and erases directed to a ddresses between them (inclusive) must be blocked by hardwa re. the base and limit fields are ignored when this bit is cleared. 30:29 reserved 28:16 protected range limit ? r/w. this field corresponds to fla address bits 24:12 and specifies the upper limit of th e protected range. address bi ts 11:0 are assumed to be fffh for the limit comparison. any address gr eater than the value programmed in this field is unaffected by this protected range. 15 read protection enable ? r/w. when set, this bit indicates that the base and limit fields in this register are valid and that read directed to a ddresses between them (inclusive) must be blocked by hardware. the base and limit fields are ignored when this bit is cleared. 14:13 reserved 12:0 protected range base ? r/w. this field corresponds to fla address bits 24:12 and specifies the lower base of the protected ra nge. address bits 11: 0 are assumed to be 000h for the base comparison. any address le ss than the value programmed in this field is unaffected by this protected range. http://www..net/ datasheet pdf - http://www..net/ serial peripheral interface (spi) 790 datasheet 22.1.18 ssfs?software sequenci ng flash status register (spi memory mapped co nfiguration registers) memory address: spibar + 90h attribute: ro, r/wc default value: 00h size: 8 bits note: the software sequencing control and status registers are reserv ed if the hardware sequencing control and status registers are used. bit description 7:5 reserved 4 access error log (ael) ? ro. this bit reflects the valu e of the hardware sequencing status ael register. 3 flash cycle error (fcerr) ? r/wc. hardware sets this bit to 1 when a programmed access is blocked from running on the spi inte rface due to one of the protection policies or when any of the programmed cycle registers is written while a programmed access is already in progress. this bit remains asserted until cleared by software writing a 1 or hardware reset due to a global reset or ho st partition reset in an intel me enabled system. 2 cycle done status ? r/wc. the ich sets this bit to 1 when the spi cycle completes (i.e., scip bit is 0) after software sets the go bit. this bit remains asserted until cleared by software writing a 1 or hardware reset due to a global reset or host partition reset in an intel me enabled system. when this bit is set and the spi smi# enable bit is set, an internal signal is asserted to the smi# generation block. software must make sure this bit is cleared prior to enabling the spi smi# assertion for a new programmed access. 1 reserved 0 spi cycle in progress (scip) ? ro. hardware sets this bit when software sets the spi cycle go bit in the command register. th is bit remains set until the cycle completes on the spi interface. hardware automatically se ts and clears this bi t so that software can determine when read data is valid and/or when it is safe to begin programming the next command. softwa re must only program the next command when this bit is 0. http://www..net/ datasheet pdf - http://www..net/ datasheet 791 serial peripheral interface (spi) 22.1.19 ssfc?software sequenci ng flash control register (spi memory mapped configuration registers) memory address: spibar + 91h attribute: r/w default value: 000000h size: 24 bits bit description 23:19 reserved 18:16 spi cycle frequency (scf) ? r/w. this register sets frequency to use for all spi software sequencing cycles (write, erase, fa st read, read status, etc.) except for the read cycle which always run at 20 mhz. 000 = 20 mhz 001 = 33 mhz all other values reserved. this register is locked when the sp i configuration lock-down bit is set. 15 spi smi# enable (sme) ? r/w. when set to 1, the spi asserts an smi# request whenever the cycle done status bit is 1. 14 data cycle (ds) ? r/w. when set to 1, there is data that corresponds to this transaction. when 0, no data is delivered for this cycle, and the dbc and data fields themselves are don?t cares 13:8 data byte count (dbc) ? r/w. this field specifies the number of bytes to shift in or out during the data portion of the spi cycle. the valid settings (in decimal) are any value from 0 to 63. the number of byte s transferred is the value of this field plus 1. note that when this field is 00_0000b, then there is 1 byte to transfer and that 11_1111b means there are 64 bytes to transfer. 7 reserved 6:4 cycle opcode pointer (cop) ? r/w. this field selects one of the programmed opcodes in the opcode menu to be used as the spi command/opcode. in the case of an atomic cycle sequence, this determines the second command. 3 sequence prefix opcode pointer (spop) ? r/w. this field selects one of the two programmed prefix opcodes for us e when performing an atomic cycle sequence. a value of 0 points to the opcode in the least significant byte of the prefix opcodes register. by making this programmable, the ich supports flash devices that have different opcodes for enabling writ es to the data space vs. status register. 2 atomic cycle sequence (acs) ? r/w. when set to 1 along with the scgo assertion, the ich10 will execute a sequence of commands on the spi interface without allowing the lan component to arbitrate and interleave cycles. the sequence is composed of: ? atomic sequence prefix command (8-bit opcode only) ? primary command specified below by so ftware (can include address and data) ? polling the flash status register (opcode 05h) until bit 0 becomes 0b. the spi cycle in progress bit remains se t and the cycle done status bit remains unset until the busy bit in the flash status register returns 0. 1 spi cycle go (scgo) ? r/ws. this bit always returns 0 on reads. however, a write to this register with a 1 in this bit starts the spi cycle defi ned by the other bits of this register. the ?spi cycle in progress ? (scip) bit gets set by this action. hardware must ignore writes to this bi t while the cycle in progress bit is set. hardware allows other bits in this re gister to be programmed for the same transaction when writing this bit to 1. this saves an additional memory write. 0 reserved http://www..net/ datasheet pdf - http://www..net/ serial peripheral interface (spi) 792 datasheet 22.1.20 preop?prefix opcode configuration register (spi memory mapped co nfiguration registers) memory address: spibar + 94h attribute: r/w default value: 00 00h size: 16 bits note: this register is not writable when the flash configuration lock-down bit (spibar + 04h:15) is set. 22.1.21 optype?opcode type configuration register (spi memory mapped co nfiguration registers) memory address: spibar + 96h attribute: r/w default value: 0000h size: 16 bits entries in this register correspond to the entries in the opcode menu configuration register. note: the definition below only provides write pr otection for opcodes that have addresses associated with them. therefore, any erase or write opcodes that do not use an address should be avoided (for example, ?chip erase? and ?auto-address increment byte program?) note: this register is not writable when the spi configuration lock-down bit (spibar + 00h:15) is set. bit description 15:8 prefix opcode 1 ? r/w. software programs an spi opco de into this field that is permitted to run as the first comma nd in an atomic cycle sequence. 7:0 prefix opcode 0 ? r/w. software programs an spi opco de into this field that is permitted to run as the first comma nd in an atomic cycle sequence. bit description 15:14 opcode type 7 ? r/w. see the description for bits 1:0 13:12 opcode type 6 ? r/w. see the description for bits 1:0 11:10 opcode type 5 ? r/w. see the description for bits 1:0 9:8 opcode type 4 ? r/w. see the description for bits 1:0 7:6 opcode type 3 ? r/w. see the description for bits 1:0 5:4 opcode type 2 ? r/w. see the description for bits 1:0 3:2 opcode type 1 ? r/w. see the description for bits 1:0 1:0 opcode type 0 ? r/w. this field specifies informat ion about the corresponding opcode 0. this information allows the hardwa re to 1) know whether to use the address field and 2) provide bios and shared flash pr otection capabilities. the encoding of the two bits is: 00 = no address associated with this opcode; read cycle type 01 = no address associated with this opcode; write cycle type 10 = address required; read cycle type 11 = address required; write cycle type http://www..net/ datasheet pdf - http://www..net/ datasheet 793 serial peripheral interface (spi) 22.1.22 opmenu?opcod e menu configur ation register (spi memory mapped configuration registers) memory address: spibar + 98h attribute: r/w default value: 0000000000000000h size: 64 bits eight entries are available in this register to give bios a sufficient set of commands for communicating with the flash device, while also restricting what malicious software can do. this keeps the hardware flexible enough to operate with a wide variety of spi devices. note: it is recommended that bios avoid progra mming write enable opcodes in this menu. malicious software could then perform writes and erases to the spi flash without using the atomic cycle mechanism. this could cause functional failures in a shared flash environment. write enable opcodes should only be programmed in the prefix opcodes. this register is not writable when the spi configuration lock-down bit (spibar + 00h:15) is set. bit description 63:56 allowable opcode 7 ? r/w. see the description for bits 7:0 55:48 allowable opcode 6 ? r/w. see the description for bits 7:0 47:40 allowable opcode 5 ? r/w. see the description for bits 7:0 39:32 allowable opcode 4 ? r/w. see the description for bits 7:0 31:24 allowable opcode 3 ? r/w. see the description for bits 7:0 23:16 allowable opcode 2 ? r/w. see the description for bits 7:0 15:8 allowable opcode 1 ? r/w. see the description for bits 7:0 7:0 allowable opcode 0 ? r/w. software programs an spi opco de into this field for use when initiating spi commands through the control register. http://www..net/ datasheet pdf - http://www..net/ serial peripheral interface (spi) 794 datasheet 22.1.23 bbar?bios base addres s configuration register (spi memory mapped co nfiguration registers) memory address: spibar + a0h attribute: r/w, ro default value: 00000000h size: 32 bits eight entries are available in this register to give bios a sufficient set of commands for communicating with the flash device, while also restricting what malicious software can do. this keeps the hardware flexible enough to operate with a wide variety of spi devices. 22.1.24 fdoc?flash desc riptor observability control register (spi memory mapped co nfiguration registers) memory address: spibar + b0h attribute: r/w default value: 00000000h size: 32 bits note: this register that can be used to observe the contents of the flash descriptor that is stored in the ich10 flash controller. this regi ster is only applicable when spi device is in descriptor mode. bit description 31:24 reserved 23:8 bottom of system flash ? r/w. this field determines the bo ttom of the system bios. the ich10 will not run programmed commands nor memory reads whose address field is less than this value. this field corresponds to bits 23:8 of the 3- byte address; bits 7:0 are assumed to be 00h for th is vector when comparing to a potential spi address. note: the spi host controller prevents an y programmed cycle using the address register with an address less than the va lue in this register . some flash devices specify that the read id command must have an address of 0000h or 0001h. if this command must be supported with th ese device, it must be performed with the bios bar 7:0 reserved bit description 31:15 reserved 14:12 flash descriptor section select (fdss) ? r/w. selects which section within the loaded flash descriptor to observe. 000 = flash signature and descriptor map 001 = component 010 = region 011 = master 111 = reserved 11:2 flash descriptor section index (fdsi) ? r/w. selects the dw offset within the flash descriptor section to observe. 1:0 reserved http://www..net/ datasheet pdf - http://www..net/ datasheet 795 serial peripheral interface (spi) 22.1.25 fdod?flash descriptor ob servability data register (spi memory mapped configuration registers) memory address: spibar + b4h attribute: ro default value: 00000000h size: 32 bits note: this register that can be used to observe the contents of the flash descriptor that is stored in the ich10 flash controller. 22.1.26 afc?additional fl ash control register (spi memory mapped configuration registers) memory address: spibar + c0h attribute: ro, r/w default value: 00000000h size: 32 bits. bit description 31:0 flash descriptor section data (fdsd) ? ro. returns the dw of data to observe as selected in the flash descriptor observability control. bit description 31:3 reserved. 2:1 flash controller in terface dynamic cloc k gating enable ? r/w. 0 = flash controller interface dy namic clock gating is disabled 1 = flash controller interface dy namic clock gating is enabled other configurations are reserved. 0 flash controller core dynamic clock gating enable ? r/w. 0 = flash controller core dynamic clock gating is disabled 1 = flash controller core dynamic clock gating is enabled http://www..net/ datasheet pdf - http://www..net/ serial peripheral interface (spi) 796 datasheet 22.1.27 lvscc? host lower ve ndor specific component capabilities register (spi memory mapped co nfiguration registers) memory address: spibar + c4h attribute: ro, rwl default value: 00000000h size: 32 bits note: all attributes described in lvscc must apply to all flash space below the fpba, even if it spans between two separate flash parts. th is register is only applicable when spi device is in descriptor mode. bit description 31:24 reserved. 23 vendor component lock (lvcl) ? rw. this register locks itself when set. 0 = the lock bit is not set 1 = the vendor component lock bit is set. 22:16 reserved 15:8 lower erase opcode (leo) ? rw. this register is prog rammed with the flash erase instruction opcode required by the vendor?s flash component. this register is locked by the vendor component lock (lvcl) bit. 7:5 reserved 4 write enable on write status (lwews) ? rw. this register is locked by the vendor component lock (lvcl) bit. 0 = no requirement to write to the status register prior to a write 1 = a write of 00h to the spi flash?s status re gister is required prior to write and erase to unlock the flash component. 06h is the opcode used to unlock the status register. notes: 1. this is not an atomic se quence. if the spi component?s status register is non- volatile, then bios should issue an atomic software sequence cycle to unlock the flash part. 2. this bit should not be set to 1 if the spi flash status register is non-volatile. this may lead to premature flash wear out. 3. bit 3 and bit 4 should not be both set to 1. 3 lower write status required (lwsr) ? rw. this register is locked by the vendor component lock (lvcl) bit. 0 = no requirement to write to the status register prior to a write 1 = a write of 00h to the spi flash?s status re gister is required prior to write and erase to unlock the flash component. 50h is the opcode used to unlock the status register. notes: 1. this is not an atomic se quence. if the spi component?s status register is non- volatile, then an atomic so ftware sequencing should be used to unlock the flash part. note: this bit should not be set to 1 if the spi flash status register is non-volatile. this may lead to premature flash wear out. note: bit 3 and bit 4 should not be both set to 1. http://www..net/ datasheet pdf - http://www..net/ datasheet 797 serial peripheral interface (spi) 22.1.28 uvscc? host upper ve ndor specific component capabilities register (spi memory mapped configuration registers) memory address: spibar + c8h attribute: ro, rwl default value: 00000000h size: 32 bits note: all attributes described in uvscc must apply to all flash space equal to or above the fpba, even if it spans between two separate fl ash parts. this register is only applicable when spi device is in descriptor mode. 2 lower write granularity (lwg) ? rw . this register is locked by the vendor component lock (lvcl) bit. 0 = 1 byte 1 = 64 byte notes: 1. if more than one flash component exists , this field must be set to the lowest common write granularity of th e different flash components. 2. if using 64 b write, bios must ensure that multiple byte writes do not occur over 256 b boundaries. this will lead to corru ption as the write will wrap around the page boundary on the spi flash part. this is a a feature page writeable spi flash. 1:0 lower block/sector erase size (lbes)? rw. this field identifies the erasable sector size for all flash components. 00 = 256 byte 01 = 4 kb 10 = 8 kb 11 = 64 kb this register is locked by the vendor component lock (lvcl) bit. hardware takes no action base d on the value of this regi ster. the contents of this register are to be used only by software an d can be read in the hsfsts.berase register in both the bios and the gbe program registers if fla is less than fpba. bit description bit description 31:24 reserved. 23 vendor component lock (uvcl) ? rw. 0 = the lock bit is not set 1 = the vendor component lock bit is set. this register locks itself when set. 22:16 reserved 15:8 upper erase opcode (ueo) ? rw. this register is prog rammed with the flash erase instruction opcode required by the vendor?s flash component. this register is locked by the vendor component lock (uvcl) bit. 7:5 reserved http://www..net/ datasheet pdf - http://www..net/ serial peripheral interface (spi) 798 datasheet 4 write enable on write status (uwews) ? rw.this register is locked by the vendor component lock (uvcl) bit. 0 = no requirement to write to the status register prior to a write 1 = a write of 00h to the spi flash?s status re gister is required prior to write and erase to unlock the flash component. 06h is the opcode used to unlock the status register. notes: 1. this is not an atomic se quence. if the spi component?s status register is non- volatile, then bios should issue an atomic software sequence cycle to unlock the flash part. 2. this bit should not be set to 1 if the spi flash status register is non-volatile. this may lead to premature flash wear out. 3. bit 3 and bit 4 should not be both set to 1. 3 upper write status required (uwsr) ? rw. this register is locked by the vendor component lock (uvcl) bit. 0 = no requirement to write to the status register prior to a write 1 = a write of 00h to the spi flash?s status re gister is required prior to write and erase to unlock the flash component. 50h is the opcode used to unlock the status register. notes: 1. this is not an atomic se quence. if the spi component?s status register is non- volatile, then an atomic so ftware sequencing should be used to unlock the flash part. 2. this bit should not be set to 1 if the spi flash status register is non-volatile. this may lead to premature flash wear out. 3. bit 3 and bit 4 should not be both set to 1. 2 upper write granularity (uwg) ? rw. this register is locked by the vendor component lock (uvcl) bit. 0 = 1 byte 1 = 64 byte notes: 1. if more than one flash component exists , this field must be set to the lowest common write granularity of th e different flash components. 2. if using 64 b write, bios must ensure that multiple byte writes do not occur over 256 b boundaries. this will lead to corru ption as the write will wrap around the page boundary on the spi fl ash part. this is a a featur e page writea ble spi flash. 1:0 upper block/sector erase size (ubes)? rw. this field identifies the erasable sector size for all flash components. valid bit settings: 00 = 256 byte 01 = 4 kb 10 = 8 kb 11 = 64 kb this register is locked by the vendor component lock (uvcl) bit. hardware takes no action based on the valu e of this register. th e contents of this register are to be used only by software an d can be read in the hsfsts.berase register in both the bios and the gbe program regist ers if fla is greater or equal to fpba. bit description http://www..net/ datasheet pdf - http://www..net/ datasheet 799 serial peripheral interface (spi) 22.1.29 fpb ? flash partition boundary (spi memory mapped configuration registers) memory address: spibar + d0h attribute: ro default value: 00000000h size: 32 bits note: this register is only applicable when spi device is in descriptor mode. bit description 31:13 reserved. 12:0 flash partition bound ary address (fpba) ? ro. this register reflects the value of flash descriptor component fpba field. http://www..net/ datasheet pdf - http://www..net/ serial peripheral interface (spi) 800 datasheet 22.2 flash descriptor registers the following sections describe the data structure of the flash descriptor on the spi device. these are not registers within ich10. 22.2.1 flash desc riptor content 22.2.1.1 flvalsig - flash valid sign ature register (flash descriptor registers) memory address: fdbar + 000h default value: h size: 32 bits 22.2.1.2 flmap0 - flash map 0 regist er (flash descriptor registers) memory address: fdbar + 004h default value: h size: 32 bits bits description 31:0 flash valid signature. this field identifies the flash de scriptor sector as valid. if the contents at this location contain 0ff0a55ah, then the flash descriptor is considered valid and it will operate in descriptor mode, else it will operate in non-descriptor mode. bits description 31:27 reserved 26:24 number of regions (nr). this field identifies the total number of flash regions. this number is 0's based, so a setting of all 0's in dicates that the only fl ash region is region 0, the flash desc riptor region. 23:16 flash region base address (frba). this identifies address bi ts [11:4] for the region portion of the flash descriptor. bi ts [24:12] and bits [3:0] are 0. a recommended frba is 04h. 15:10 reserved 9:8 number of components (nc) . this field identifies the total number of flash components. each supported flash compon ent requires a separate chip select. 00 = 1 component. 01 = 2 components. all other settings = reserved 7:0 flash component base address (fcba) . this identifies address bits [11:4] for the component portion of the flash descript or. bits [24:12] and bits [3:0] are 0. a recommended fcba is 01h. http://www..net/ datasheet pdf - http://www..net/ datasheet 801 serial peripheral interface (spi) 22.2.1.3 flmap1?flash map 1 regist er (flash descriptor registers) memory address: fdbar + 008h default value: h size: 32 bits 22.2.1.4 flmap2?flash map 2 regist er (flash descriptor registers) memory address: fdbar + 00ch default value: h size: 32 bits bits description 31:24 ich strap length (isl). identifies the 1s based number of dwords of ich straps to be read, up to 255 dws (1kb) max. a setting of all 0's indicates there are no ich dw straps. 23:16 flash ich strap base address (fisba). this identifies addres s bits [11:4] for the ich strap portion of the flash descriptor. bits [24:12] and bits [3:0] are 0. for validation purposes, th e recommended fisba is 10h 15:11 reserved 10:08 number of masters (nm). this field identifies the total number of flash regions. this number is 0's based. 7:0 flash master base address (fmba). this identifies addres s bits [11:4] for the master portion of the flash descriptor. bits [24:12] and bits [3:0] are 0. a recommended fmba is 06h. bits description 31:16 reserved 15:08 mch strap length (msl). identifies the 1's based num ber of dwords of (g)mch straps to be read, up to 25 5 dws (1kb) max. a setting of all 0's indicates there are no (g)mch dw straps. 7:0 flash (g)mch strap base address (fmsba). this identifies address bits [11:4] for the (g)mch strap portion of the flash descriptor. bits [24:12] and bits [3:0] are 0. a recommended fmsba is 20h. http://www..net/ datasheet pdf - http://www..net/ serial peripheral interface (spi) 802 datasheet 22.2.2 flash descriptor component section the following section of the flash descriptor is used to identify the different flash components and their capabilities. 22.2.2.1 flcomp?flash components register (flash descriptor registers) memory address: fcba + 000h default value: h size: 32 bits bits description 31:30 reserved 29:27 read id and read status clock frequency . 000 = 20 mhz 001 = 33 mhz all other settings = reserved note: if more than one flash component exists, this field must be set to the lowest common frequency of the di fferent flash components. 26:24 write and erase clock frequency . 000 = 20 mhz 001 = 33 mhz all other settings = reserved note: if more than one flash component exists, this field must be set to the lowest common frequency of the di fferent flash components. 23:21 fast read cl ock frequency . this field identifies the frequency that can be used with the fast read instruction. this field is unde fined if the fast read support field is '0'. 000 = 20 mhz 001 = 33 mhz all other settings = reserved note: if more than one flash component exists, this field must be set to the lowest common frequency of the di fferent flash components. 20 fast read support . 0 = fast read is not supported 1 = fast read is supported if the fast read support bit is a '1' and a de vice issues a direct re ad or issues a read command from the hardware se quencer and the length is gr eater than 4 bytes, then the spi flash instruction should be "fast read". if the fast read support is a '0' or the length is 1-4 bytes, then the spi flash instruction should be "read". reads to the flash descriptor always us e the read command independent of the setting of this bit. note: if more than one flash component exists, th is field can only be set to '1' if both components support fast read. http://www..net/ datasheet pdf - http://www..net/ datasheet 803 serial peripheral interface (spi) 19:17 read clock frequency . 000 = 20 mhz all other settings = reserved note: if more than one flash comp onent exists, this field must be set to the lowest common frequency of the di fferent flash components. 16:6 reserved 5:3 component 2 density. this field identifies the size of the 2nd flash component. if there is not 2nd flash component, the contents of this field are undefined. 000 = 512 kb 001 = 1 mb 010 = 2 mb 011 = 4 mb 100 = 8 mb 101 = 16 mb 111 = reserved 2:0 component 1 density. this field identifies the si ze of the 1st or only flash component. 000 = 512 kb 001 = 1 mb 010 = 2 mb 011 = 4 mb 100 = 8 mb 101 = 16 mb 111 = reserved this field is defaulted to "101b" (16 mb) after reset. in non-descriptor mode, only one flash component is supported and all accesses to flash will be to this component. bits description http://www..net/ datasheet pdf - http://www..net/ serial peripheral interface (spi) 804 datasheet 22.2.2.2 flill?flash invalid instruct ions register (flash descriptor registers) memory address: fcba + 004h default value: h size: 32 bits 22.2.2.3 flpb?flash partitio n boundary register (flash descriptor registers) memory address: fcba + 008h default value: h size: 32 bits bits description 31:24 invalid instruction 3 . see definition of invalid instruction 0 23:16 invalid instruction 2 . see definition of invalid instruction 0 15:8 invalid instruction 1 . see definition of invalid instruction 0 7:0 invalid instruction 0 . op-code for an invalid instru ction in the that the flash controller should protect against such as chip erase. this byte should be set to 0 if there are no invalid instructions to protect against for this field. op-codes programmed in the software sequencing opcode menu configuration and prefix-opcode configuration are not allowed o use any of the invalid instructions listed in this register. bits description 31:13 reserved 12:0 flash partition boundary address (fpba) . this register specifies flash boundary address bits[24:12] that logi cally divides the flash space into two partitions, a lower and an upper partition. the lo wer and upper partitions can support spi flash parts with different attributes between partitions that are defined in the lvscc and uvscc. note: all flash space in each partition must have the same in the vscc attributes, even if it spans between different flash parts. note: if this register is set to all 0s, then there is only one partition, the upper partition, and the entire address space ha s uniform erasable sector sizes, write granularity, and write state required se ttings. the fpba mu st reside on an erasable sector boundary. http://www..net/ datasheet pdf - http://www..net/ datasheet 805 serial peripheral interface (spi) 22.2.3 flash descriptor region section the following section of the flash descriptor is used to identify the different flash regions flash regions: ? if a particular region is not using spi flash, the particular region should be disabled by setting the region base to all 1's, and the region limit to all 0's (base is higher than the limit) ? for each region except flreg0, the flas h controller must have a default region base of fffh and the region limit to 000h within the flash controller in case the number of regions specifies that a region is not used. 22.2.3.1 flreg0?flash region 0 (flash descriptor) register (flash descriptor registers) memory address: frba + 000h default value: h size: 32 bits 22.2.3.2 flreg1?flash region 1 (bios) register (flash descriptor registers) memory address: frba + 004h default value: h size: 32 bits bits description 31:29 reserved 28:16 region limit. this specifies address bits 24:12 for the region limit. 15:13 reserved 12:0 region base. this specifies address bits 24:12 for the region base. bits description 31:29 reserved 28:16 region limit. this specifies address bits 24:12 for the region limit. 15:13 reserved 12:0 region base. this specifies address bits 24:12 for the region base. note: if the bios region is not used, the re gion base must be programmed to 1fffh and the region limit to 0000h to disable the region. http://www..net/ datasheet pdf - http://www..net/ serial peripheral interface (spi) 806 datasheet 22.2.3.3 flreg2?flash region 2 (me) register (flash descriptor registers) memory address: frba + 008h default value: h size: 32 bits 22.2.3.4 flreg3?flash region 3 (gbe) re gister (flash descriptor registers) memory address: frba + 00ch default value: h size: 32 bits 22.2.3.5 flreg4?flash region 4 (platfor m data) register (flash descriptor registers) memory address: frba + 010h default value: h size: 32 bits bits description 31:29 reserved 28:16 region limit. this specifies address bits 24:12 for the region limit. 15:13 reserved 12:0 region base. this specifies address bits 24:12 for the region base. note: if the intel management engine region is not used, the region base must be programmed to 1fffh and the region li mit to 0000h to disable the region. bits description 31:29 reserved 28:16 region limit. this specifies address bits 24:12 for the region limit. note: the maximum region limit is 128kb above the region base. 15:13 reserved 12:0 region base. this specifies address bits 24:12 for the region base. note: if the gbe region is not used, the regi on base must be programmed to 1fffh and the region limit to 0000h to disable the region. bits description 31:29 reserved 28:16 region limit. this specifies address bits 24:12 for the region limit. note: the maximum region limit is 128kb above the region base. 15:13 reserved 12:0 region base. this specifies address bits 24:12 for the region base. note: if the platform data region is not used , the region base must be programmed to 1fffh and the region limit to 0000h to disable the region. http://www..net/ datasheet pdf - http://www..net/ datasheet 807 serial peripheral interface (spi) 22.2.4 flash descriptor master section 22.2.4.1 flmstr1?flash master 1 (host cpu/ bios) (flash descriptor registers) memory address: fmba + 000h default value: h size: 32 bits bits description 31:29 reserved, must be zero 28 platform data region write access . if the bit is set, this master can erase and write that particular region th rough register accesses. 27 gbe region write access . if the bit is set, this master can erase and write that particular region thro ugh register accesses. 26 me region write access . if the bit is set, this master can erase and write that particular region thro ugh register accesses. 25 host cpu/bios master region write access . if the bit is set, this master can erase and write that particular regi on through register accesses. bit 25 is a don?t care as the primary master always has read/write permissions to it?s primary region 24 flash descriptor region write access . if the bit is set, this master can erase and write that particular region through register accesses. 23:21 reserved, must be zero 20 platform data region read access . if the bit is set, this master can read that particular region thro ugh register accesses. 19 gbe region read access . if the bit is set, this master can read that particular region through register accesses. 18 me region read access . if the bit is set, this master can read that particular region through register accesses. 17 host cpu/bios master region read access . if the bit is set, this master can read that particular region th rough register accesses. bit 17 is a don?t care as the primary master always has read/write permissions to it?s primary region 16 flash descriptor region read access . if the bit is set, this master can read that particular region thro ugh register accesses. 15:0 requester id . this is the requester id of the ho st processor. this must be set to 0000h. http://www..net/ datasheet pdf - http://www..net/ serial peripheral interface (spi) 808 datasheet 22.2.4.2 flmstr2?flash master 2 (m e) (flash descriptor registers) memory address: fmba + 004h default value: h size: 32 bits bits description 31:29 reserved, must be zero 28 platform data region write access . if the bit is set, this master can erase and write that particular region through register accesses. 27 gbe region write access . if the bit is set, this master can erase and write that particular region thro ugh register accesses. 26 me master region write access . if the bit is set, this master can erase and write that particular region through register accesses. bit 26 is a don?t care as the primary master always has read/write permissions to it?s primary region 25 host cpu/bios re gion write access . if the bit is set, this master can erase and write that particular region through register accesses. 24 flash descriptor re gion write access . if the bit is set, this master can erase and write that particular region through register accesses. 23:21 reserved, must be zero 20 platform data region read access . if the bit is set, this master can read that particular region thro ugh register accesses. 19 gbe region read access . if the bit is set, this master can read that particular region through register accesses. 18 me master region read access . if the bit is set, this master can read that particular region through re gister accesses. bit 18 is a don?t care as the primary master always has read/write permissions to it?s primary region 17 host cpu/bios region read access . if the bit is set, this master can read that particular region thro ugh register accesses. 16 flash descriptor region read access . if the bit is set, this master can read that particular region thro ugh register accesses. 15:0 requester id . this is the requester id of the in tel management engine. this must be set to 0000h. http://www..net/ datasheet pdf - http://www..net/ datasheet 809 serial peripheral interface (spi) 22.2.4.3 flmstr3?flash master 3 (g be) (flash descriptor registers) memory address: fmba + 008h default value: h size: 32 bits bits description 31:29 reserved, must be zero 28 platform data region write access . if the bit is set, this master can erase and write that particular region through register accesses. 27 gbe master region write access . if the bit is set, this master can erase and write that particular region th rough register accesses. bit 27 is a don?t care as the primary master always has read/write permissions to it?s primary region 26 me region write access . if the bit is set, this master can erase and write that particular region thro ugh register accesses. 25 host cpu/bios re gion write access . if the bit is set, this master can erase and write that particular region through register accesses. 24 flash descriptor re gion write access . if the bit is set, this master can erase and write that particular region through register accesses. 23:21 reserved, must be zero 20 platform data region read access . if the bit is set, this master can read that particular region thro ugh register accesses. 19 gbe master region read access . if the bit is set, this master can read that particular region thro ugh register accesses. bit 19 is a don?t care as the primary master always has read/write permissions to it?s primary region 18 me region read access . if the bit is set, this master can read that pa rticular region through register accesses. 17 host cpu/bios region read access . if the bit is set, this master can read that particular region thro ugh register accesses. 16 flash descriptor region read access . if the bit is set, this master can read that particular region thro ugh register accesses. 15:0 requester id . this is the requester id of the gbe. this must be set to 0218h. http://www..net/ datasheet pdf - http://www..net/ serial peripheral interface (spi) 810 datasheet 22.2.5 descriptor upper map section 22.2.5.1 flumap1?flash upper map 1 (flash descriptor registers) memory address: fdbar + efch default value: 0000ffffh size: 32 bits 22.2.6 intel me vendor specific component capabilities table entries in this table allow support for a spi flash part for intel ? quiet system technology. bios will still need to set up the proper vscc registers for bios and integrated gigabit ethernet usage. each vscc table entry is composed of two 32 bit fields: jedec id and the corresponding vscc value. 22.2.6.1 jid0?jedec-id 0 register (flash descriptor registers) memory address: vtba + 000h default value: size: 32 bits bits default description 31:16 0 reserved 15:8 1 me vscc table length (vtl). identifies the 1s based number of dwords contained in the vscc table. each spi component entry in the table is 2 dwords long. 7:0 1 me vscc table base address (vtba). this identifies address bits [11:4] for the vscc table portion of the flash descriptor. bits [24:12] and bits [3:0] are 0. note: vtba should be above the o ffset for mchstrp0 and below flumap1. it is recomm ended that this address is set based on the anticipated maximum number of different flash parts entries. bits description 31:24 reserved 23:16 spi component device id 1. this field identifies the second byte of the device id of the spi flash component. this is the third byte returned by the read jedec-id command (opcode 9fh). 15:8 spi component device id 0. this field identifies the first byte of the device id of the spi flash component. this is the second byte returned by the read jedec-id command (opcode 9fh). 7:0 spi component vendor id. this field identifies the one byte vendor id of the spi flash component. this is the first byte returned by the read jedec-id command (opcode 9fh). http://www..net/ datasheet pdf - http://www..net/ datasheet 811 serial peripheral interface (spi) 22.2.6.2 vscc0?vendor specific component capab ilities 0 (flash descriptor registers) memory address: vtba + 004h default value: size: 32 bits note: in this table ?lower? applies to characteristics of all flash space below the flash partition boundary address (fpba). ?upper? applies to characteristics of all flash space above the fpba. bits description 31:16 lower erase opcode (leo). this register must be programmed with the flash erase instruction opcode that corresponds to the erase size that is in lbes. 23:21 reserved 20 lower write enable on write status (lwews) . 0 = no write to the spi flash?s status register required prior to a write 1 = a write of 00h to the spi flash?s status re gister is required prior to write and erase to unlock the flash component. 06h is the opcode used to unlock the status register. notes: 1. this bit should not be set to 1 if the spi flash status register is non-volatile. this may lead to premature flash wear out. 2. bit 20 and bit 19 should not be both set to 1. 19 lower write status required (lwsr) . 0 = no requirement to write to the status register prior to a write 1 = a write of 00h to the spi flash?s status re gister is required prior to write and erase to unlock the flash component. 50h is the opcode used to unlock the status register. notes: 1. bit 20 and bit 19 should not be both set to 1. 2. bit 19 should not be set if the flash part does not support the opcode 50h to unlock the status register. 18 lower write granularity (lwg) . 0 = 1 byte 1 = 64 byte 17:16 lower block/sector erase size (lbes). this field identifies the erasable sector size for all flas h space below the flash partition boundary address. 00 = 256 byte 01 = 4 kb 10 = 8 kb 11 = 64 kb 15:8 upper erase opcode (ueo). this register must be prog rammed with the flash erase instruction opcode that corresponds to the erase size that is in lbes. 7:5 reserved http://www..net/ datasheet pdf - http://www..net/ serial peripheral interface (spi) 812 datasheet 22.2.6.3 jidn?jedec-id register n (flash descriptor registers) memory address: vtba + (n*8)h default value: size: 32 bits note: ?n? is an integer denoting the in dex of the intel me vscc table. 4 upper write enable on write status (uwews) . 0 = no write to the spi flash?s status register required prior to a write 1 = a write of 00h to the spi flash?s status re gister is required pr ior to write and erase to unlock the flash component. 06h is the opcode used to unlock the status register. notes: 1. this bit should not be set to 1 if the spi flash status register is non-volatile. this may lead to premature flash wear out. 2. bit 4 and bit 3 should not be both set to 1. 3 upper write status required (uwsr) . 0 = no requirement to write to the status register prior to a write 1 = a write of 00h to the spi flash?s status re gister is required pr ior to write and erase to unlock the flash component. 50h is the opcode used to unlock the status register. notes: 1. bit 4 and bit 3 should not be both set to 1. 2. bit 3 should not be set if the flash pa rt does not support the opcode 50h to unlock the status register. 2 upper write granularity (uwg) . 0 = 1 byte 1 = 64 bytes 1:0 upper block/sector erase size (ubes). this field identifies the erasable sector size for all flash components. 00 = 256 bytes 01 = 4 kb 10 = 8 kb 11 = 64 kb bits description bits description 31:24 reserved 23:16 spi component device id 1. this field identifies the second byte of the device id of the spi flash component. this is the thir d byte returned by the read jedec-id command (opcode 9fh). 15:8 spi component device id 0. this field identifies the firs t byte of the device id of the spi flash component. this is the seco nd byte returned by the read jedec-id command (opcode 9fh). 7:0 spi component vendor id. this field identifies the one byte vendor id of the spi flash component. this is the first byte returned by the read jedec-id command (opcode 9fh). http://www..net/ datasheet pdf - http://www..net/ datasheet 813 serial peripheral interface (spi) 22.2.6.4 vsccn?vendor specific compon ent capabilities n (flash descriptor registers) memory address: vtba + 004h + (n*8)h default value: size: 32 bits note: ?n? is an integer denoting the in dex of the intel me vscc table. note: in this table ?lower? applies to characteristics of all flash space below the flash partition boundary address (fpba). ?upper? applies to characteristics of all flash space above the fpba. bits description 31:16 lower erase opcode (leo). this field must be prog rammed with the flash erase instruction opcode that corresponds to the erase size th at is in lbes. 23:21 reserved 20 lower write enable on write status (lwews) . 0 = no write to the spi flash?s status register required prior to a write 1 = a write of 00h to the spi flash?s status register is required prior to write and erase to unlock the flash component. 06h is th e opcode used to unlock the status register. notes: 1. this bit should not be set to 1 if the spi flash status register is non-volatile. this may lead to prem ature flash wear out. 2. bit 20 and bit 19 should not be both set to 1. 19 lower write status required (lwsr) . 0 = no requirement to write to the status register prior to a write 1 = a write of 00h to the spi flash?s status register is required prior to write and erase to unlock the flash component. 50h is th e opcode used to unlock the status register. notes: 1. bit 20 and bit 19 should not be both set to1. 2. bit 19 should not be set if the flash pa rt does not support the opcode 50h to unlock the status register. 18 lower write granularity (lwg) . 0 = 1 byte 1 = 64 byte 17:16 lower block/sector erase size (lbes) . this field identifies the erasable sector size for all flash space below the flash partition boundary address. valid bit settings: 00 = 256 byte 01 = 4 kb 10 = 8 kb 11 = 64 kb 15:8 upper erase opcode (ueo) . this field must be progra mmed with the flash erase instruction opcode that corresponds to the erase size th at is in lbes. 7:5 reserved http://www..net/ datasheet pdf - http://www..net/ serial peripheral interface (spi) 814 datasheet 4 upper write enable on write status (uwews) . 0 = no write to the spi flash?s status register required prior to a write 1 = a write of 00h to the spi flash?s status register is required prior to write and erase to unlock the flash component. 06h is the opcode used to unlock the status register. notes: 1. this bit should not be set to 1 if the spi flash status regist er is non-volatile. this may lead to premature flash wear out. 2. bit 4 and bit 3 should not be both set to 1. 3 upper write status required (uwsr) . 0 = no requirement to write to the status register prior to a write 1 = a write of 00h to the spi flash?s status register is required prior to write and erase to unlock the flash component. 50h is the opcode used to unlock the status register. notes: 1. bit 4 and bit 3 should not be both set to 1. 2. bit 3 should not be set if the flash pa rt does not support the opcode 50h to unlock the status register. 2 upper write granularity (uwg) . 0 = 1 byte 1 = 64 bytes 1:0 upper block/sector erase size (ubes) . this field identifies the erasable sector size for all flash components. 00 = 256 bytes 01 = 4 kb 10 = 8 kb 11 = 64 kb bits description http://www..net/ datasheet pdf - http://www..net/ datasheet 815 serial peripheral interface (spi) 22.3 oem section memory address: f00h default value: size: 256 bytes 256 bytes are reserved at the top of the flash descriptor for use by the oem. the information stored by the oem can only be written during the manufacturing process as the flash descriptor read/write permission s must be set to read only when the computer leaves the manufacturing floor. the ich flash controller does not read this information. ffh is suggested to reduce programming time. 22.4 gbe spi flash program registers the gbe flash registers are memory-mapped with a base address mbarb found in the gbe lan register chapter device 25: function 0: offset 14h. the individual registers are then accessible at mbarb + offset as indicated in the following table. these memory mapped registers must be accessed in byte, word, or dword quantities. note: these register are only applicable when spi flash is used in descriptor mode. table 22-2. gigabit lan spi flas h program register address map (gbe lan memory mapped configuration registers) mbarb + offset mnemonic register name default type 00h?03h glfpr gigabit lan flash primary region 00000000h ro 04h?05h hsfsts hardware sequencing flash status 0000h ro, r/wc, r/w 06h?07h hsfctl hardware sequencing flash control 0000h r/w, r/ws 08h?0bh faddr flash address 00000000h r/w 0ch?0fh reserved reserved 00000000h 10h?13h fdata0 flash data 0 00000000h r/w 14h?4fh reserved reserved 00000000h 50h?53h frap flash region access permissions 00000000h ro, r/w 54h?57h freg0 flash region 0 00000000h ro 58h?5bh freg1 flash region 1 00000000h ro 5ch?5f freg2 flash region 2 00000000h ro 60h?63h freg3 flash region 3 00000000h ro 64h?73h reserved reserved for future flash regions 74h?77h fpr0 flash protected range 0 00000000h r/w 78h?7bh fpr1 flash protected range 1 00000000h r/w 7ch?8fh reserved reserved 90h ssfsts software sequencing flash status 00h ro, r/w 91h?93h ssfctl software sequencing flash control 000000h r/w 94h?95h preop prefix opcode configuration 0000h r/w 96h?97h optype opcode type configuration 0000h r/w 98h?9fh opmenu opcode menu configuration 00000000 00000000h r/w a0h?dfh reserved reserved http://www..net/ datasheet pdf - http://www..net/ serial peripheral interface (spi) 816 datasheet 22.4.1 glfpr ?gigabit lan flas h primary region register (gbe lan memory mapped configuration registers) memory address: mbarb + 00h attribute: ro default value: 00000000h size: 32 bits bit description 31:29 reserved 28:16 gbe flash primary region limit (prl)? ro. this specifies address bits 24:12 for the primary region limit. the value in this register loaded from the contents in the flash descriptor.flreg3.region limit 15:13 reserved 12:0 gbe flash primary region base (prb) ? ro. this specifies address bits 24:12 for the primary region base the value in this register is load ed from the contents in the flash descriptor.flreg3.region base http://www..net/ datasheet pdf - http://www..net/ datasheet 817 serial peripheral interface (spi) 22.4.2 hsfs?hardware sequencing flash status register (gbe lan memory mapped configuration registers) memory address: mbarb + 04h attribute: ro, r/wc, r/w default value: 0000h size: 16 bits bit description 15 flash configuration lock-down (flockdn) ? r/w. when set to 1, those flash program registers that are locked down by this flockdn bit cannot be written. once set to 1, this bit can only be cleared by a hardware reset du e to a global reset or host partition reset in an intel me enabled system. 14 flash descriptor valid (fdv)? ro. this bit is set to a 1 if the flash controller read the correct flash descriptor signature. if the flash descriptor valid bit is not ?1?, software cannot use the hardware sequencing registers, but must use the software sequencing registers. any attempt to use the hardware sequencing registers will result in the fcerr bit being set. 13 flash descriptor override pin strap status (fdopss)? ro. this bit reflects the value the flash descriptor override pin-strap. 0 = no override 1 = the flash descriptor override strap is set 12:6 reserved 5 spi cycle in progress (scip)? ro. hardware sets this bi t when software sets the flash cycle go (fgo) bit in the hardware se quencing flash control register. this bit remains set until the cycle completes on the spi interface. hardware automatically sets and clears this bit so that software can dete rmine when read data is valid and/or when it is safe to begin programming the next command. software must only program the next command when this bit is 0. 4:3 block/sector eras e size (berase) ? ro. this field identifies the erasable sector size for all flash components. 00 = 256 byte 01 = 4 k byte 10 = 8 k byte 11 = 64 k byte if the fla is less than fpba then this field reflects the value in the lvscc.lbes register. if the fla is greater or equal to fpba th en this field reflec ts the value in the uvscc.ubes register. 2 access error log (ael) ? r/w/c. hardware sets this bit to a 1 when an attempt was made to access the bios region using the di rect access method or an access to the bios program registers that violated the security restrictions. this bit is simply a log of an access security violatio n. this bit is cleared by software writing a ?1? 1 flash cycle error (fcerr) ? r/w/c. hardware sets this bit to 1 when an program register access is blocked to the flash due to one of the protection policies or when any of the programmed cycle registers is wr itten while a programmed access is already in progress. this bit remains asserted until cleared by so ftware writing a 1 or until hardware reset occurs due to a global rese t or host partition re set in an intel me enabled system. software must clear this bit before settin g the flash cycle go bit in this register. 0 flash cycle done (fdone) ? r/w/c. the ich sets this bit to 1 when the spi cycle completes after software previously set the fgo bit. this bit re mains asserted until cleared by software writing a 1 or hardware re set due to a global re set or host partition reset in an intel me enabled system. when this bit is set and the spi smi# enable bit is set, an internal signal is asserted to the smi# genera tion block. soft ware must make sure this bit is cleared prio r to enabling the spi smi# as sertion for a new programmed access. http://www..net/ datasheet pdf - http://www..net/ serial peripheral interface (spi) 818 datasheet 22.4.3 hsfc?hardware sequencing flash control register (gbe lan memory mapped configuration registers) memory address: mbarb + 06h attribute: r/w, r/ws default value: 0000h size: 16 bits 22.4.4 faddr?flash address register (gbe lan memory mapped configuration registers) memory address: mbarb + 08h attribute: r/w default value: 00000000h size: 32 bits bit description 15:10 reserved 9:8 flash data byte count (fdbc) ? r/w. this field specifies the number of bytes to shift in or out during the data portion of the spi cycle. the content?s of this register are 0s based with 0b representi ng 1 byte and 11b representing 4 bytes. the number of bytes transferred is the value of this field plus 1. this field is ignored for the block erase command. 7:3 reserved 2:1 flash cycle (fcycle) ? r/w. this field defines the flash spi cycle type generated to the flash when the fgo bit is set as defined below: 00 = read (1 up to 4 bytes by setting fdbc) 01 = reserved 10 = write (1 up to 4 bytes by setting fdbc) 11 = block erase 0 flash cycle go (fgo) ? r/w/s. a write to this register with a ?1? in this bit initiates a request to the flash spi arbiter to start a cy cle. this register is cleared by hardware when the cycle is granted by the spi arbiter to run the cycle on the spi bus. when the cycle is complete, the fdone bit is set. software is forbidden to write to any regist er in the hsflctl register between the fgo bit getting set and the fdone bi t being cleared. any attempt to violate this rule will be ignored by hardware. hardware allows other bits in this register to be progra mmed for the same transaction when writing this bit to 1. this saves an additional memory write. this bit always returns 0 on reads. bit description 31:25 reserved 24:0 flash linear address (fla) ? r/w. the fla is the starting byte linear address of a spi read or write cycle or an address with in a block for the bloc k erase command. the flash linear address must fall within a region for which bi os has access permissions. http://www..net/ datasheet pdf - http://www..net/ datasheet 819 serial peripheral interface (spi) 22.4.5 fdata0?flash data 0 register (gbe lan memory mapped configuration registers) memory address: mbarb + 10h attribute: r/w default value: 00000000h size: 32 bits bit description 31:0 flash data 0 (fd0) ? r/w. this field is shifted out as the spi data on the master-out slave-in data pin during the data portion of the spi cycle. this register also shifts in the data from th e master-in slave-out pin into this register during the data portion of the spi cycle. the data is always shifted starting with the least significant byte, msb to lsb, followed by the next least significant byte, msb to lsb, etc. specifically, the shift order on spi in terms of bits within this register is: 7-6-5-4-3-2-1-0-15-14-13-?8-23-22-?16-31?24 bit 24 is the last bit shifted out/in. there are no alignment assumptions; byte 0 always represents the value specif ied by the cycle address. note that the data in this register may be modified by the hardware during any programmed spi transaction. direct memory re ads do not modify the contents of this register. http://www..net/ datasheet pdf - http://www..net/ serial peripheral interface (spi) 820 datasheet 22.4.6 frap?flash regions access permissions register (gbe lan memory mapped configuration registers) memory address: mbarb + 50h attribute: ro, r/w default value: 00000808h size: 32 bits bit description 31:28 reserved 27:25 gbe master write access grant (gmwag) ? r/w. each bit 27:25 corresponds to master[3:1]. gbe can grant one or more ma sters write access to the gbe region 3 overriding the permissions in the flash descriptor. master[1] is host cpu/bios, master[2] is intel management engine, master[3] is host processor/gbe. the contents of this register are locked by the flockdn bit. 24:20 reserved 19:17 gbe master read access grant (gmrag) ? r/w. each bit 19:17 corresponds to master[3:1]. gbe can grant one or more masters read access to the gbe region 3 overriding the read permissi ons in the flash descriptor. master[1] is host processor/bios, master[2] is intel management engine, master[3] is gbe. the contents of this register are locked by the flockdn bit 16:12 reserved 11:8 gbe region write access (grwa) ? ro. each bit 11:8 corresponds to regions 3:0. if the bit is set, this master can erase and write that particular re gion through register accesses. the contents of this register are that of the flash descriptor. flash master 3.master region write access or a part icular master has granted gb e write permissions in their master write access grant register or the fl ash descriptor security override strap is set. 7:4 reserved 3:0 gbe region read access (grra) ? ro. each bit 3:0 corresp onds to regions 3:0. if the bit is set, this master can read that particular region thro ugh register accesses. the contents of this register are that of the flash descriptor. flash master 3.master region write access or a particular master has granted gbe read permissions in their master read access grant register. http://www..net/ datasheet pdf - http://www..net/ datasheet 821 serial peripheral interface (spi) 22.4.7 freg0?flash region 0 (f lash descriptor) register (gbe lan memory mapped configuration registers) memory address: mbarb + 54h attribute: ro default value: 00000000h size: 32 bits 22.4.8 freg1?flash region 1 (bios descriptor) register (gbe lan memory mapped configuration registers) memory address: mbarb + 58h attribute: ro default value: 00000000h size: 32 bits 22.4.9 freg2?flash regi on 2 (me) register (gbe lan memory mapped configuration registers) memory address: mbarb + 5ch attribute: ro default value: 00000000h size: 32 bits bit description 31:29 reserved 28:16 region limit (rl) ? ro. this specifies address bits 24:12 for the region 0 limit. the value in this register is load ed from the contents in the flash descriptor.flreg 0.region limit 15:13 reserved 12:0 region base (rb) ? ro. this specifies address bits 24:12 for the region 0 base the value in this register is load ed from the contents in the flash descriptor.flreg0.region base bit description 31:29 reserved 28:16 region limit (rl) ? ro. this specifies address bits 24:12 for the region 1 limit. the value in this register is load ed from the contents in the flash descriptor.flreg 1.region limit. 15:13 reserved 12:0 region base (rb) ? ro. this specifies address bits 24:12 for the region 1 base the value in this register is load ed from the contents in the flash descriptor.flreg1.region base. bit description 31:29 reserved 28:16 region limit (rl) ? ro. this specifies address bits 24:12 for the region 2 limit. the value in this register is load ed from the contents in the flash descriptor.flreg 2.region limit. 15:13 reserved 12:0 region base (rb) ? ro. this specifies address bits 24:12 for the region 2 base the value in this register is load ed from the contents in the flash descriptor.flreg2.region base. http://www..net/ datasheet pdf - http://www..net/ serial peripheral interface (spi) 822 datasheet 22.4.10 freg3?flash regi on 3 (gbe) register (gbe lan memory mapped configuration registers) memory address: mbarb + 60h attribute: ro default value: 00000000h size: 32 bits 22.4.11 fpr0?flash protec ted range 0 register (gbe lan memory mapped configuration registers) memory address: mbarb + 74h attribute: r/w default value: 00000000h size: 32 bits note: this register can not be written when the flockdn bit is set to 1. bit description 31:29 reserved 28:16 region limit (rl) ? ro. this specifies address bits 24:12 for the region 3 limit. the value in this register is load ed from the contents in the flash descriptor.flreg 3.region limit. 15:13 reserved 12:0 region base (rb) ? ro. this specifies address bits 24:12 for the region 3 base the value in this register is load ed from the contents in the flash descriptor.flreg3.region base. bit description 31 write protection enable ? r/w. when set, this bit indicates that the base and limit fields in this register are va lid and that writes and erases directed to addresses between them (inclusive) must be bl ocked by hardware. the base and limit fields are ignored when this bit is cleared. 30:29 reserved 28:16 protected range limit ? r/w. this field corresponds to fla address bits 24:12 and specifies the upper limit of th e protected range. address bi ts 11:0 are assumed to be fffh for the limit comparison. any address gr eater than the value programmed in this field is unaffected by this protected range. 15 read protection enable ? r/w. when set, this bit indicates that the base and limit fields in this register are valid and that read directed to a ddresses between them (inclusive) must be blocked by hardware. th e base and limit fiel ds are ignored when this bit is cleared. 14:13 reserved 12:0 protected range base ? r/w. this field corresponds to fla address bits 24:12 and specifies the lower base of the protected ra nge. address bits 11:0 are assumed to be 000h for the base comparison. any address less than the value programmed in this field is unaffected by this protected range. http://www..net/ datasheet pdf - http://www..net/ datasheet 823 serial peripheral interface (spi) 22.4.12 fpr1?flash protected range 1 register (gbe lan memory mapped configuration registers) memory address: mbarb + 78h attribute: r/w default value: 00000000h size: 32 bits note: this register can not be written when the flockdn bit is set to 1. bit description 31 write protection enable ? r/w. when set, this bit indicates that the base and limit fields in this register are va lid and that writes and erases directed to addresses between them (inclusive) must be blocked by hardwa re. the base and limit fields are ignored when this bit is cleared. 30:29 reserved 28:16 protected range limit ? r/w. this field corresponds to fla address bits 24:12 and specifies the upper limit of th e protected range. address bi ts 11:0 are assumed to be fffh for the limit comparison. any address gr eater than the value programmed in this field is unaffected by this protected range. 15 read protection enable ? r/w. when set, this bit indicates that the base and limit fields in this register are valid and that read directed to a ddresses between them (inclusive) must be blocked by hardware. th e base and limit fields are ignored when this bit is cleared. 14:13 reserved 12:0 protected range base ? r/w. this field corresponds to fla address bits 24:12 and specifies the lower base of the protected ra nge. address bits 11: 0 are assumed to be 000h for the base comparison. any address less than the value programmed in this field is unaffected by this protected range. http://www..net/ datasheet pdf - http://www..net/ serial peripheral interface (spi) 824 datasheet 22.4.13 ssfs?software sequenci ng flash status register (gbe lan memory mapped configuration registers) memory address: mbarb + 90h attribute: ro, r/wc default value: 00h size: 8 bits note: the software sequencing control and status registers are reserv ed if the hardware sequencing control and status registers are used. bit description 7:5 reserved 4 access error log (ael) ? ro. this bit reflects the value of the hardware sequencing status ael register. 3 flash cycle error (fcerr) ? r/wc. hardware sets this bit to 1 when a programmed access is blocked from running on the spi inte rface due to one of the protection policies or when any of the programmed cycle registers is written while a programmed access is already in progress. this bit remains asserted until cleared by software writing a 1 or hardware reset due to a global reset or ho st partition reset in an intel me enabled system. 2 cycle done status ? r/wc. the ich sets this bit to 1 when the spi cycle completes (i.e., scip bit is 0) after software sets the go bit. this bit remains asserted until cleared by software writing a 1 or hardware re set due to a global re set or host partition reset in an intel me enabled system. when this bit is set and the spi smi# enable bit is set, an internal signal is as serted to the smi# generation block. software must make sure this bit is cleared prior to enabling the spi smi# assertion for a new programmed access. 1 reserved 0 spi cycle in progress (scip) ? ro. hardware sets this bit when software sets the spi cycle go bit in the command register. th is bit remains set until the cycle completes on the spi interface. hardware automatically se ts and clears this bi t so that software can determine when read data is valid and/or when it is safe to begin programming the next command. softwa re must only program the next command when this bit is 0. http://www..net/ datasheet pdf - http://www..net/ datasheet 825 serial peripheral interface (spi) 22.4.14 ssfc?software sequenci ng flash control register (gbe lan memory mapped configuration registers) memory address: mbarb + 91h attribute: r/w default value: 000000h size: 24 bits bit description 23:19 reserved 18:16 spi cycle frequency (scf) ? r/w. this register sets frequency to use for all spi software sequencing cycles (w rite, erase, fast read, read status, etc.) except for the read cycle which always run at 20mhz. 000 = 20 mhz 001 = 33 mhz all other values = reserved. this register is locked when the sp i configuration lock-down bit is set. 15 reserved 14 data cycle (ds) ? r/w. when set to 1, there is data that corresponds to this transaction. when 0, no data is delivered for this cycle, and the dbc and data fields themselves are don?t cares 13:8 data byte count (dbc) ? r/w. this field specifies the number of bytes to shift in or out during the data portion of the spi cycl e. the valid settings (in decimal) are any value from 0 to 3. the number of bytes transf erred is the value of this field plus 1. note that when this field is 00b, then ther e is 1 byte to transfer and that 11b means there are 4 bytes to transfer. 7 reserved 6:4 cycle opcode pointer (cop) ? r/w. this field selects one of the programmed opcodes in the opcode menu to be used as the spi command/opcode. in the case of an atomic cycle sequence, this de termines the second command. 3 sequence prefix opcode pointer (spop) ? r/w. this field selects one of the two programmed prefix opcodes for use when performing an atomic cycle sequence. a value of 0 points to the opcode in the least significant byte of the prefix opcodes register. by making this programmable, the ich supports flash devices that have different opcodes for enabling writes to the data space vs. status register. 2 atomic cycle sequence (acs) ? r/w. when set to 1 along with the scgo assertion, the ich will execute a sequence of commands on the spi interface without allowing the lan component to arbitrate and interleave cycles. the sequence is composed of: ? atomic sequence prefix command (8-bit opcode only) ? primary command specified below by so ftware (can include address and data) ? polling the flash status register (opcode 05h) until bit 0 becomes 0b. the spi cycle in progress bit remains set an d the cycle done status bit remains unset until the busy bit in the flash status register returns 0. 1 spi cycle go (scgo) ? r/ws. this bit always returns 0 on reads. however, a write to this register with a ?1? in this bit starts th e spi cycle defined by th e other bits of this register. the ?spi cycle in progress? (scip) bi t gets set by this action. hardware must ignore writes to this bit while the cycle in progress bit is set. hardware allows other bits in this register to be progra mmed for the same transaction when writing this bit to 1. this saves an additional memory write. 0 reserved http://www..net/ datasheet pdf - http://www..net/ serial peripheral interface (spi) 826 datasheet 22.4.15 preop?prefix opcode configuration register (gbe lan memory mapped configuration registers) memory address: mbarb + 94h attribute: r/w default value: 00 00h size: 16 bits note: this register is not writable when the spi configuration lock-down bit (mbarb + 00h:15) is set. 22.4.16 optype?opcode type configuration register (gbe lan memory mapped configuration registers) memory address: mbarb + 96h attribute: r/w default value: 0000h size: 16 bits entries in this register correspond to the entries in the opcode menu configuration register. note: the definition below only provides write pr otection for opcodes that have addresses associated with them. therefore, any erase or write opcodes that do not use an address should be avoided (for example, ?chip erase? and ?auto-address increment byte program?). note: this register is not writable when the spi configuration lock-down bit (mbarb + 00h:15) is set. bit description 15:8 prefix opcode 1 ? r/w. software programs an spi opco de into this field that is permitted to run as the first comma nd in an atomic cycle sequence. 7:0 prefix opcode 0 ? r/w. software programs an spi opco de into this field that is permitted to run as the first comma nd in an atomic cycle sequence. bit description 15:14 opcode type 7 ? r/w. see the description for bits 1:0 13:12 opcode type 6 ? r/w. see the description for bits 1:0 11:10 opcode type 5 ? r/w. see the description for bits 1:0 9:8 opcode type 4 ? r/w. see the description for bits 1:0 7:6 opcode type 3 ? r/w. see the description for bits 1:0 5:4 opcode type 2 ? r/w. see the description for bits 1:0 3:2 opcode type 1 ? r/w. see the description for bits 1:0 1:0 opcode type 0 ? r/w. this field specifies informat ion about the corresponding opcode 0. this information allows the hardwa re to 1) know whether to use the address field and 2) provide bios and shared flash pr otection capabilities. the encoding of the two bits is: 00 = no address associated with this opcode; read cycle type 01 = no address associated with this opcode; write cycle type 10 = address required; read cycle type 11 = address required; write cycle type http://www..net/ datasheet pdf - http://www..net/ datasheet 827 serial peripheral interface (spi) 22.4.17 opmenu?opcod e menu configur ation register (gbe lan memory mapped configuration registers) memory address: mbarb + 98h attribute: r/w default value: 0000000000000000h size: 64 bits eight entries are available in this register to give gbe a sufficient set of commands for communicating with the flash device, while also restricting what malicious software can do. this keeps the hardware flexible enough to operate with a wide variety of spi devices. note: it is recommended that gbe avoid programmi ng write enable opcodes in this menu. malicious software could then perform writes and erases to the spi flash without using the atomic cycle mechanism. this could cause functional failures in a shared flash environment. write enable opcodes should only be programmed in the prefix opcodes. this register is not writable when the spi configuration lock-down bit (mbarb + 00h:15) is set. bit description 63:56 allowable opcode 7 ? r/w. see the description for bits 7:0 55:48 allowable opcode 6 ? r/w. see the description for bits 7:0 47:40 allowable opcode 5 ? r/w. see the description for bits 7:0 39:32 allowable opcode 4 ? r/w. see the description for bits 7:0 31:24 allowable opcode 3 ? r/w. see the description for bits 7:0 23:16 allowable opcode 2 ? r/w. see the description for bits 7:0 15:8 allowable opcode 1 ? r/w. see the description for bits 7:0 7:0 allowable opcode 0 ? r/w. software programs an spi opco de into this field for use when initiating spi commands through the control register. http://www..net/ datasheet pdf - http://www..net/ serial peripheral interface (spi) 828 datasheet http://www..net/ datasheet pdf - http://www..net/ datasheet 829 thermal sensor registers (d31:f6) 23 thermal sensor registers (d31:f6) 23.1 pci bus configuration registers table 23-1. thermal sensor register address map offset mnemonic register name default type 00h?01h vid vendor identification 8086h ro 02h?03h did device identification tbd ro 04h?05h cmd command register 0000h r/w, ro 06h?07h sts device status 0010h r/wc, ro 08h rid revision id 00h ro 09h pi programming interface 00h ro 0ah scc sub class code 80h ro 0bh bcc base class code 11h ro 0ch cls cache line size 00h ro 0dh lt latency timer 00h ro 0eh htype header type 00h ro 0fh bist built-in self test 00h ro 10h?13h tbar thermal base address (memory) 00000004h r/w, ro 14h?17h tbarh thermal base address high dword 00000000h ro 2ch?2dh svid subsystem vendor identifier 0000h r/wo 2eh?2fh sid subsystem identifier 0000h r/wo 34h cap_ptr capabilities pointer 50h ro 3ch intln interrupt line 00h rw 3dh intpn interrupt pin tbd ro 40h?43h tbarb bios assigned thermal base address 00000004h r/w, ro 44h?47h tbarbh bios assigned ba high dword 00000000h r/w 50h?51h pid power management identifiers 0001h ro 52h?53h pc power management capabilities 0022h ro 54h?57h pcs power management control and status 0000h r/w, ro http://www..net/ datasheet pdf - http://www..net/ thermal sensor registers (d31:f6) 830 datasheet 23.1.1 vid?vendor identification offset address: 00h ? 01h attribute: ro default value: 8086h size: 16 bit lockable: no power well: core 23.1.2 did?device identification offset address: 02h ? 03h attribute: ro default value: tbd size: 16 bit 23.1.3 cmd?command address offset: 04h ? 05h attribute: ro, r/w default value: 0000h size: 16 bits bit description 15:0 vendor id ? ro. this is a 16-bit value as signed to intel. intel vid = 8086h bit description 15:0 device id (did) ? ro. indicates the device number assigned by the sig. bit description 15:11 reserved 10 interrupt disable (id) ? rw. enables the device to assert an intx#. 0 = when cleared, the intx# signal may be asserted. 1 = when set, the thermal logic?s in tx# signal will be de-asserted. 9 fbe (fast back to back enable) ? ro. not implemented. hardwired to 0. 8 sen (serr enable) ? ro. not implemented. hardwired to 0. 7 wcc (wait cycle control) ? ro. not implemented. hardwired to 0. 6 per (parity error response) ? ro. not implemented. hardwired to 0. 5 vps (vga palette snoop) ? ro. not implemented. hardwired to 0. 4 mwi (memory write and invalidate enable ) ? ro. not implemented. hardwired to 0. 3 sce (special cycle enable) ? ro. not implemented. hardwired to 0. 2 bme (bus master enable) ? ro. not implemented. hardwired to 0. 1 memory space enable (mse) ? rw. 0 = disable 1 = enable. enables memory space ac cesses to the thermal registers. 0 ios (i/o space) ? ro. the thermal logic does not implement io space; therefore, this bit is hardwired to 0. http://www..net/ datasheet pdf - http://www..net/ datasheet 831 thermal sensor registers (d31:f6) 23.1.4 sts?status address offset: 06h ? 07h attribute: r/wc, ro default value: 0010h size: 16 bits 23.1.5 rid?revision identification address offset: 08h attribute: ro default value: 00h size: 8 bits 23.1.6 pi? progra mming interface address offset: 09h attribute: ro default value: 00h size: 8 bits bit description 15 detected parity error (dpe) ? r/wc. this bit is set whenever a parity error is seen on the internal interface for this function, regardless of the setting of bit 6 in the command register. software cl ears this bit by writing a ?1? to this bit location. 14 serr# status (serrs) ? ro. not implemented. hardwired to 0. 13 received master abort (rma) ? ro. not implemented. hardwired to 0. 12 received target abort (rta) ? ro. not implemented. hardwired to 0. 11 signaled target-abort (sta) ? ro. not implemented. hardwired to 0. 10:9 devsel# timing status (devt) ? ro. does not apply. hardwired to 0. 8 master data parity error (mdpe) ? ro. not implemented. hardwired to 0. 7 fast back to back capable (fbc) ? ro. does not apply. hardwired to 0. 6reserved 5 66 mhz capable (c66) ? ro. does not apply. hardwired to 0. 4 capabilities list exists (clist) ? ro. indicates that the controller contains a capabilities pointer list. the fi rst item is pointed to by l ooking at configuration offset 34h. 3 interrupt status (is) ? ro. reflects the state of the intx# signal at the input of the enable/disable circuit. this bit is a 1 when the intx# is asserted. this bit is a 0 after the interrupt is cleared (indep endent of the state of the interrupt disabl e bit in the command register). 2:0 reserved bit description 7:0 revision id (rid) ? ro. indicates the device sp ecific revision identifier. bit description 7:0 programming interface (pi) ? ro. ich thermal logic has no standard programming interface. http://www..net/ datasheet pdf - http://www..net/ thermal sensor registers (d31:f6) 832 datasheet 23.1.7 scc?sub class code address offset: 0ah attribute: ro default value: 80h size: 8 bits 23.1.8 bcc?base class code address offset: 0bh attribute: ro default value: 11h size: 8 bits 23.1.9 cls?cache line size address offset: 0ch attribute: ro default value: 00h size: 8 bits 23.1.10 lt?latency timer address offset: 0dh attribute: ro default value: 00h size: 8 bits 23.1.10.1 htype?header type address offset: 0eh attribute: ro default value: 00h size: 8 bits bit description 7:0 sub class code (scc) ? ro. value assigned to ich thermal logic. bit description 7:0 base class code (bcc) ? ro. value assigned to ich thermal logic. bit description 7:0 cache line size (cls) ? ro. does not apply to pci bus target-only devices. bit description 7:0 latency timer (lt) ? ro. does not apply to pci bus target-only devices. bit description 7 multi-function device (mfd) ? ro. this bit is 0 becaus e a multi-function device only needs to be marked as such in functi on 0, and the thermal registers are not in function 0. 6:0 header type (htype) ? ro. implements type 0 configuration header. http://www..net/ datasheet pdf - http://www..net/ datasheet 833 thermal sensor registers (d31:f6) 23.1.11 bist?built-in self test address offset: 0fh attribute: ro default value: 00h size: 8 bits 23.1.12 tbar?thermal base address offset: 10h ? 13h attribute: rw, ro default value: 00000004h size: 32 bits this bar creates 4k bytes of memory spac e to signify the base address of thermal memory mapped configuration registers. this memory space is active when the command (cmd) register memory space enable (mse) bit is set and either tbar[31:12] or tbarh are programmed to a non-zero address. this bar is owned by the operating system, and allows the os to locate the thermal registers in system memory space. 23.1.13 tbarh?thermal base high dword address offset: 14h ? 17h attribute: rw, ro default value: 00000000h size: 32 bits this bar extension holds the high 32 bits of the 64 bit tbar. in conjunction with tbar, it creates 4 kb of memory space to sign ify the base address of thermal memory mapped configuration registers. bit description 7:0 built-in self test (bist) ? ro. not implemented. hardwired to 00h. bit description 31:12 thermal base address (tba) ? rw. this field provides the base address for the thermal logic memory mapped configuration registers. 4 kb byte s are requested by hardwiring bits 11:4 to 0s. 11:4 reserved 3 prefetchable (pref) ? ro. indicates that this bar is not pre-fetchable. 2:1 address range (addrng) ? ro. indicates that this bar can be located anywhere in 64 bit address space. 0 space type (sptyp) ? ro. indicates that this bar is located in memory space. bit description 31:0 thermal base address high (tbah) ? rw. tbar bits 61:32. http://www..net/ datasheet pdf - http://www..net/ thermal sensor registers (d31:f6) 834 datasheet 23.1.14 svid?subsystem vendor id address offset: 2ch ? 2dh attribute: r/wo default value: 0000h size: 16 bits this register should be implemented for any function that could be instantiated more than once in a given system. the svid regi ster, in combination with the subsystem id register, enables the operating environment to distinguish one subsystem from the other(s). software (bios) will write the value to this register. after that, the value can be read, but writes to the register will have no ef fect. the write to this register should be combined with the write to the sid to create one 32-bit write. this register is not affected by d3 hot to d0 reset. 23.1.15 sid?subsystem id address offset: 2eh ? 2fh attribute: r/wo default value: 0000h size: 16 bits this register should be implemented for any function that could be instantiated more than once in a given system. the sid register, in combination with the subsystem vendor id register make it possible for the operating environment to distinguish one subsystem from the other(s). software (bios) will write the value to this register. after that, the value can be read, but writes to the register will have no ef fect. the write to this register should be combined with the write to the svid to create one 32-bit write. this register is not affected by d3 hot to d0 reset. 23.1.16 cap_ptr ?cap abilities pointer address offset: 34h attribute: ro default value: 50h size: 8 bits 23.1.17 offset 3ch ? intln?interrupt line address offset: 3ch attribute: rw default value: 00h size: 8 bits bit description 15:0 svid (svid) ? r/wo. these rwo bits have no ich10 functionality. bit description 15:0 sid (said) ? r/wo. these rwo bits have no ich10 functionality. bit description 7:0 capability pointer (cp) ? ro. indicates that the first capa bility pointer offset is offset 50h (power management capability). bit description 7:0 interrupt line ? rw. ich10 hardware does not use th is field directly. it is used to communicate to software the interrupt line that the interrupt pin is connected to. http://www..net/ datasheet pdf - http://www..net/ datasheet 835 thermal sensor registers (d31:f6) 23.1.18 intpn?interrupt pin address offset: 3dh attribute: ro default value: tbd size: 8 bits 23.1.19 tbarb?bios assigned thermal base address address offset: 40h ? 43h attribute: rw,ro default value: 00000004h size: 32 bits this bar creates 4 kb of memory space to signify the base address of thermal memory mapped configuration registers. this memory space is active when tbarb.sptypen is asserted. this bar is owned by the bios, an d allows the bios to locate the thermal registers in system memory space. if both tbar and tbarb are programmed, then the os and bios each have their own independ ent ?view? of the thermal registers, and must use the tsiu, tciu, and tbiu registers to denote thermal registers ownership/ availability. 23.1.20 tbarbh?bios assigned thermal base high dword address offset: 44h ? 47h attribute: rw default value: 00000000h size: 32 bits this bar extension holds the high 32 bits of the 64 bit tbarb. bit description 7:4 reserved 3:0 interrupt pin ? ro. this reflects the value of the device 31 interrupt pin bits 27:24 (ttip) in chipset configuration space. bit description 31:12 thermal base address (tba) ? rw. this field provides th e base address for the thermal logic memory mapped configuration registers. 4k b byte s are requested by hardwiring bits 11:4 to 0s. 11:4 reserved 3 prefetchable (pref) ? ro. indicates that this bar is not pre-fetchable. 2:1 address range (addrng) ? ro. indicates that this bar can be located anywhere in 64 bit address space. 0 space type enable (sptypen) ? rw. 0 = disable. 1 = enable. when set to 1b by software, enables the decode of this memory bar. bit description 31:0 thermal base address high (tbah) ? rw. tbar bits 61:32. http://www..net/ datasheet pdf - http://www..net/ thermal sensor registers (d31:f6) 836 datasheet 23.1.21 pid?pci power mana gement capability id address offset: 50h ? 51h attribute: ro default value: 0001h size: 16 bits 23.1.22 pc?power management capabilities address offset: 52h ? 53h attribute: ro default value: 0022h size: 16 bits bit description 15:8 next capability (next) ? ro. indicates that this is the last capability structure in the list. 7:0 cap id (cap) ? ro. indicates that this pointer is a pci power management capability bit description 15:11 pme_support ? ro. indicates pme# is not supported 10 d2_support ? ro. the d2 state is not supported. 9 d1_support ? ro. the d1 state is not supported. 8:6 aux_current ? ro. pme# from d3cold state is not su pported, therefore this field is 000b. 5 device specific initialization (dsi) ? ro. indicates that device-specific initialization is required. 4 reserved 3 pme clock (pmec) ? ro. does not apply. hardwired to 0. 2:0 version (vs) ? ro. indicates support for revision 1.2 of the pci power management specification. http://www..net/ datasheet pdf - http://www..net/ datasheet 837 thermal sensor registers (d31:f6) 23.1.23 pcs?power management control and status address offset: 54h ? 57h attribute: rw, ro default value: 0000h size: 32 bits bit description 31:24 data ? ro. does not apply. hardwired to 0s. 23 bus power/clock control enable (bpcce) ? ro. hardwired to 0. 22 b2/b3 support (b23) ? ro. does not apply. hardwired to 0. 21:16 reserved 15 pme status (pmes) ? ro. this bit is always 0, since this pci function does not generate pme# 14:9 reserved 8 pme enable (pmee) ? ro. this bit is always zero, sinc e this pci function does not generate pme# 7:4 reserved 3 no soft reset ? ro. when set (1), this bit indicates that devices transitioning from d3 hot to d0 because of powerstate command s do not perform an internal reset. configuration context is preserved. upon transition from d3 hot to d0 initialized state, no additional operating syst em intervention is required to preserve configuration context beyond writing the powerstate bits. 2reserved 1:0 power state (ps) ? r/w. this field is used both to determine the current power state of the thermal controller and to set a new power state. the values are: 00 = d0 state 11 = d3 hot state if software attempts to write a value of 10b or 01b in to this field, th e write operation must complete normally; however, the data is discarded and no state change occurs. when in the d3 hot states, the thermal controller?s co nfiguration space is available, but the i/o and memory spaces are not. additionally, interrupts are blocked. when software changes this value from the d3 hot state to the d0 st ate, no internal warm (soft) reset is generated. http://www..net/ datasheet pdf - http://www..net/ thermal sensor registers (d31:f6) 838 datasheet 23.2 thermal memory mapped configuration registers (thermal sensor - d31:f26) the base memory for these thermal memory mapped configuration registers is specified in the tbarb (d31:f6:offset 40 h). the individual registers are then accessible at tbarb + offset. there are two sensors in the ich10. each sensor has a separate configuration register set. both sensors must be configured together. 23.2.1 tsxe?thermal sensor [1:0] enable offset address: sensor 0: tbarb+01h attribute: r/w sensor 1: tbarb+41h default value: 00h size: 8 bit table 23-2. thermal memory mapped configuration register address map offset mnemonic register name default type 1h ts0e thermal sensor 0 enable 00h r/w 2h ts0s thermal sensor 0 enable 00h r/w 4h ts0ttp thermal sensor 0 catastrophic trip point 00000000h r/w 8h ts0c0 thermal sensor 0 catastrophic lock down 00h r/w 0eh ts0pc thermal sensor 0 policy control 00h r/w 41h ts1e thermal sensor 1 enable 00h r/w 42h ts1s thermal sensor 1 enable 00h r/w 44h ts1ttp thermal sensor 1 catastrophic trip point 00000000h r/w 48h ts1c0 thermal sensor 1 catastrophic lock down 00h r/w 4eh ts1pc thermal sensor 1 policy control 00h r/w 83h ts0lock thermal sensor 0 register lock control 00h r/w c3h ts1lock thermal sensor 1 re gister lock control 00h r/w bit description 7:0 thermal sensor enable (tse) ? r/w. bios shall always program this register to the value bah to enable the thermal sensor. all other values are reserved. http://www..net/ datasheet pdf - http://www..net/ datasheet 839 thermal sensor registers (d31:f6) 23.2.2 tsxs?thermal sensor[1:0] status offset address: sensor 0: tbarb+02h attribute: ro sensor 1: tbarb+42h default value: 00h size: 8 bit 23.2.3 tsxttp?thermal sensor [1:0] catastrophic trip point offset address: sensor 0: tbarb+04h attribute: r/w sensor 1: tbarb+44h default value: 00h size: 32 bit 23.2.4 tsxco?thermal sensor [1 :0] catastrophic lock-down offset address: sensor 0: tbarb+08h attribute: r/w sensor 1: tbarb+48h default value: 00h size: 8 bit bit description 7 catastrophic trip indicator (cti) ? ro. 0 = the temperature is below the catastrophic setting. 1 = the temperature is above the catastrophic setting. 6:0 reserved bit description 31:8 reserved 7:0 catastrophic trip point setting (ctps) ? r/w. these bits set the catastrophic trip point. bios will program these bits. these bits are lockab le via tsco.bit 7. bit description 7 lock bit for catastrophic (lbc) ? r/w. 0 = catastrophic programming interface is unlocked 1 = locks the catastrophic programming interface including tsttp.bits[7:0]. this bit may only be set to a 0 by a hardwa re reset. writing a 0 to this bit has no effect. 6:0 reserved http://www..net/ datasheet pdf - http://www..net/ thermal sensor registers (d31:f6) 840 datasheet 23.2.5 tsxpc?thermal sensor [1:0] policy control offset address: sensor 0: tbarb+0eh attribute: r/w sensor 1: tbarb+4eh default value: 00h size: 8 bit 23.2.6 tsxlock?thermal sensor [1:0] register lock control offset address: sensor 0: tbarb+83h attribute: r/w sensor 1: tbarb+c3h default value: 00h size: 8 bit bit description 7 policy lock-down bit ? r/w. 0 = this register can be programmed and modified. 1 = prevents writes to this register. note: tsco.bit 7 and tslock.bit2 must also be 1 when this bit is set to 1. this bit may only be set to a 0 by a hardwa re reset. writing a 0 to this bit has no effect. 6 catastrophic power-down enable ? r/w. 1 = when set to 1, the power management lo gic unconditionally transitions to the s5 state when a catastrophic temperature is detected by the sensor. 5:0 reserved bit description 7:3 reserved 2 lock control ? r/w. this bit must be set to 1 when tspc.bit7 is set to 1. 1:0 reserved http://www..net/ datasheet pdf - http://www..net/ |
Price & Availability of AF82801
 |
|
|
|
|
All Rights Reserved © IC-ON-LINE 2003 - 2022 |
| [Add Bookmark] [Contact Us] [Link exchange] [Privacy policy] |
|
Mirror Sites : [www.datasheet.hk]
[www.maxim4u.com] [www.ic-on-line.cn]
[www.ic-on-line.com] [www.ic-on-line.net]
[www.alldatasheet.com.cn]
[www.gdcy.com]
[www.gdcy.net] |